auto-enter value (sequences) won't stick

Classic Servoy
1

When setting auto-enter values for database sequences they will only stick for the session you have Developer open.
During this session you can create records without problems.
But after closing and re-launching Developer the auto-enter values of my PK columns are set to database managed values. A setting that is not compatible with the used RDBMS and/or JDBC driver.

For developers like me who use only database sequences this is a showstopper.

Servoy Developer
Version 3.1.2-build 406
Java version 1.5.0_06-64 (Mac OS X)
RDBMS: PostgreSQL 8.2.3
JDBC driver: postgresql-8.2-504.jdbc3.jar

Bugbase case # 67642

2

We have not been able to reproduce the problem.

We created a new table on a Postgres db using Developer, pk auto-enter = ‘Sequence, dbseq’, created the sequence in the db backend and were able to create records.
After restart of Developer, the settings were unchanged, as expected.

A similar test using Sybase and auto-enter db-identity also works as expected.

Please check the log files for errors.

Rob

3

Hi Rob,

Have you tried creating a table in Postgres with a SERIAL column? This will create a sequence. Then try to set this table up in Servoy.

We have had intermittent problems with this, when importing a solution onto a new Servoy server or upgrading to 3.0.

Several times I have had to reselect all the sequences in the data provider window. Very irritating.

Robert, do your pk fields in Postgres have a “Primary Key” constraint?
Without this I find Servoy get very confused.

4

Hi Christian,

Yeah, all my PK columns have a primary key constraint.
I use DbWrench to design/edit my datamodels. It takes care of all that.

In the mean time I have done some more testing.
I see the same result when I do a clean install of 3.1.2 and use Sybase as repository server instead of PostgreSQL…so something very strange is going on.
Nothing in the logs either.

Support got now my JDBC driver, solution and datamodel. We’ll see what comes out of this.

Thanks for thinking with me :)

5

We still have not been able to reproduce the problem.
The solution was imported in postgres, created the tables.
The pk auto-enter values can be changed and stick after restart of developer.

Rob

6

Hi,

We have been able to locate the problem.
There is a small problem in the column-info editor interface.
When you use the ‘Properties’ button, changes are not always saved to the database.

The workaround is simple: do not use the button, click on the Properties-cell of the column you want to modify. The same dialog appears and changes are saved.

The problem will be fixed in next release.

Rob