db info in server problem

Classic Servoy
1

Hi,
im working with servoy 6 over DBFs (using smart client) and i have a little problem.
We had a table with 3 fields marked as ‘row_ident’, at some poin we realized that was a mistake and that only 2 of those fields made the uniqueness of the record, so on the developer we modified the dbi without any trouble.
Theres a form in my solution where i do a loadRecord() passing on a dataset composed by those 2 fields and when executing it in developer i have no problem at all, the records are loaded correctly, but when running it from the server i get an error saying that the size of the pk im passing (2) doesnt match the one of the table (3), so i guess that although i modified the dbi and imported the solution again on the server the information about the row_idents was never updated.

I know there are no dbis on the server side, so where is he keeping this information? how can i tell him that now the identifiers of that table are 2 and not 3 like it used to be??

thanks in advance

2

I guess you just get a “The server version of the column X has Y constraint while in the import (…)” warning.
Try creating a pre-import hook, and in it use the maintenance plugin (getServer(…).getTable(…).getColumn(…).setFlag(…) with ROWID_COLUMN) to reset the rowID flag of that column.

3

im not being able to call the setFlag method on the column, it doesnt show up as an available method.
how is this supposed to work? could it be that the method has been deprecated or something?

4

You are probably on Servoy 5.
The method I suggested was added in 6.

5

im on Version: 6.0.0 - build 1217

6

the wiki doesnt show that method for servoy 6

http://wiki.servoy.com/display/public/DOCS/JSColumn

7

You are right. It was added in 6.0.1.

Sample:

	var pk = table.createNewColumn("id", JSColumn.MEDIA, 16); // can also use (JSColumn.TEXT, 36) for UUIDs
	pk.setFlag(JSColumn.PK_COLUMN, true);
	pk.setFlag(JSColumn.UUID_COLUMN, true)
	pk.sequenceType = JSColumn.UUID_GENERATOR

The only other option I can think of (except for modifying repository tables via query directly) is to drop the table in pre-import hook and let import recreate it.

8

well i ended up modifying the repository table, thanks for the help