i have some nice tables with
Servoy Developer
Version 3.1.6-build 410
Java version 1.5.0_07-87 (Mac OS X)
PostgreSQL 8.2.3
and database driven pkeys.
everthing is working fine.
last saterday i wanted to migrate to servoy 3.5.
wow, everthing is running, but the databse driven pkeys don’t.
i get this message from servoy:
com.servoy.j2db.ApplicationException: Cannot save form data
com.servoy.j2db.dataprocessing.DataException: ERROR: relation “asset_client_asset_client_id_seq” does not exist
the name of the sequence in postgresql is:
“seq_testtable_id” and (see attach) also in servoy.
if i change “db_identity” to “db_seq” and specify the seq to the name above and apply the changes, servoy gets back to “db_identity”.
can anyone help me?
Thanks and best regards,
Friedrich Toussaint
MacBook Pro
OS X 10.4.10
2 GB RAM
Servoy Developer
Version 3.1.6-build 410 / Version 3.5-build 513
Java version 1.5.0_07-87 (Mac OS X)
PostgreSQL 8.2.3
We use database sequences in PostgreSQL (8.2.4) in all out Servoy projects - haven’t tried 3.5 yet. There have been some problems with Servoy and database sequences in the past. try the following:
make sure the pk fields also have primary key constraints
I don’t specify the key the way you have done it in the screenshot, I do it by selecting from the ‘Sequence’ popup and use the ‘Specify’ to enter the sequence name, in your case ‘seq_testtable_id’
thanks for the answer. i did so in servoy 3.1.6 too, but if i change in 3.5 to db_seq it returns to db_identity after storing the value.
the same thing happens if i change to database value (the correct valuestring automatically is shown in the field)
MacBook Pro
OS X 10.4.10
2 GB RAM
Servoy Developer
Version 3.1.6-build 410 / Version 3.5-build 513
Java version 1.5.0_07-87 (Mac OS X)
PostgreSQL 8.2.3