Servoy 3.5 and postgres

Classic Servoy
1

hello everybody,

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”.

please also see http://forum.servoy.com/viewtopic.php?t=8948

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

Bild 1.png
Bild 1.png512×626 31.2 KB

2

thanks Johan Compagner,

he had posted two links to fix the problem with postgresql:

http://downloads.servoy.com/beta/3xx_pr … 2dbdev.jar
http://downloads.servoy.com/beta/3xx_product/j2db.jar

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

3

Hi,

I’m having the exact same problem. The .jar’s that Johan posted seemed to fix the problem (clicking ‘Apply’ at least doesnt cause it to switch back to ‘db identity’ immediately) but as soon as i restart Servoy Developer, everything is back on ‘db identity’ again.

Any ideas?

4

Friedrich,

Was the problem fixed with the new jars?

Oele,

I cannot reproduce the problem with the latest jars.
When upgrading to the download-jars, have you removed the old jars from the lib-directory (if they are only renamed, they will still be used)

Rob

5

excuse me, please, the last three weeks i have been in holydays,

i removed the old jar’s. the problem is still here, but otherwise. i’ll test next week and post here.

sincerely
friedrich toussaint

6

Hi,

What’s the status of this issue? After having stumbled upon these problems back in september i’ve just stopped using postgres sequences for some time and instead used servoy sequences.

I’m now trying to use postgres sequences again, now with Servoy 3.5.5, but i’m again having the same kind of problems.

When Servoy sees a postgresql column with a sequence it defaults to “db identity”, with the wrong (guessed?) sequence name. Setting it to “database managed” or “database default” doesn’t work - it just goes back to “database identity” as soon as i click “apply”.

Servoy sequences and “db seq” do work, and “db identity” probably also works if i would rename my sequences to the name Servoy expects, but these options are just “work-arounds” to me; i want Servoy just to “back off and use whatever value the database assigns”.

Is there still any point in trying the 2 .jar’s that were mentioned in this topic with the current version of Servoy?

7

I just found out that the problem only occurs for primary key fields. Other fields with database driven sequences/triggers work just fine. Still i would like to get it to work for pk’s as well…

8

Hello

The fixes that have been made are included in the latest release, downloading the jars is not necessary.
We were under the assumption that the problem was already solved.
As stated before, we could not reproduce this.

If you still have the problem when using version 3.5.5, please create a case in our support system.

Make sure to include a small sample solution that shows the problem and list the exact postgres version you are using.

http://forum.servoy.com/viewtopic.php?t=6789

Rob

9

OK, i have done so now. Case ID = 122359

10

This will be fixed in next release of Servoy.

Rob

11

Great. Thanks a lot!