Postgres db pk problem when importing module

Classic Servoy
1

Hi,

I just moved some modules from my test server to a production server.

These modules reference a number of tables in a PostgreSQL database.
These tables did not exist on the production server, so Servoy helpfully recreated the tables during the import.
However,

  • Although the pk fields were still set to DB generated keys, Servoy had guessed Sequence names which were wrong.
  • And Servoy did not create the sequences.

Developer: Mac OS X 10.4.2, Servoy 2.2
Repository: remote Windows XP, PostgreSQL 8.0

2

Known issue and a pet peeve of mine as well.

When you import the module through the web-interface then you get a bunch more options than in the Developer import dialog.
There you see a checkbox named “Override sequence types to the sequence types contained in the import version.”. Yes the one with the big warning.
Anyway to force Servoy to use truly DB managed keys you need to check this checkbox before importing.

I don’t remember if that will also create the sequences. I believe it does. But try it.

I suggest you remove the 3 newly created tables before you re-import the solution.

Hope this helps.

3

Hi Robert,

Thanks, I will try the checkbox with the BIG warning the next time.

By the way, do you know if Servoy will move triggers and stored procedures, or, does it just move stuff it understands?

4

Good question. I don’t know really.
I guess one of the Servoyans have to answer that.

But I think having a schema dump handy is always a save bet.

5

A best guess regarding Stored Procs would be ‘no’ to Servoy moving them as they really only exist on the DB Server and are ‘called’ from Servoy during method process ! :cry:

Cheers
Harry

6

Servoy does not move triggers and stored procedures.

7

Thank you for the info.

I will move/upgrade the databases manually to preserve sequences, triggers and stored procedures.