Here is my situation:
I have an empty repository. A working database connection to the datasource. Latest PostgreSQL driver (although I get the same result with the bundled pgsql driver).
Database is already created with db managed sequences.
In Developer, before exporting the solution, I already defined that this solution uses DB managed sequences and is working correctly.
When I import the solution into the server through the admin pages I see the following messages:
[warning]
The server version of the column 'crd_id' of table 'curadomi_ecard' in server 'curadomi' has 'servoy seq' sequence type while the import version has 'db seq' sequence type.
[warning]
The server version of the column 'usr_id' of table 'curadomi_user' in server 'curadomi' has 'servoy seq' sequence type while the import version has 'db seq' sequence type.
[warning]
The server version of the column 'pli_id' of table 'curadomi_poll_items' in server 'curadomi' has 'servoy seq' sequence type while the import version has 'db seq' sequence type.
[warning]
The server version of the column 'rcp_id' of table 'curadomi_ecard_receipt' in server 'curadomi' has 'servoy seq' sequence type while the import version has 'db seq' sequence type.
[warning]
The server version of the column 'pol_id' of table 'curadomi_poll' in server 'curadomi' has 'servoy seq' sequence type while the import version has 'db seq' sequence type.
When I try to insert data through the solution I get indeed errors because the PK’s aren’t getting filled.
Any clue why Servoy isn’t honoring predefined settings in the solution when imported into the server?
Servoy version R2 2.1.2-build 315, repository version 24
Mac OS X Server 10.3.6 and 10.3.7
I ran Developer on the server (while Servoy-Server is running) and looked at the sequence settings.
Turned out that some of them were on DB managed and some others on Servoy managed.
Also some of the DB managed listed wrong sequence names. (?)
Anyway, I changed them all by hand to DB managed with the correct sequence name and tried to insert data through a client.
Still errors.
So I restarted the Servoy Server.
Same result.
I figured the problem must have to do with the datasource settings/cache so I looked under Database servers in the Servoy Admin pages.
After clicking the Update Table Sequences the client would let me do inserts.
My question is this:
Why doesn’t a restart of Servoy Server check those datasource settings?
Should I always run this function before importing new solutions?
Why doesn’t Servoy Server honor my solution settings?
Servoy should never ever mess with sequences unless you ask. This is just too critical.
Question 2)
Nope, you don’t need to run this function at all.
Question 3)
Servoy Server will honor your solution settings when you check the box which says “override sequence types to the sequence types contained in the import version”.
The default is not to do this. The default is to leave sequences alone. This has the maybe unexpected effect that when you start the repository for the first time Servoy assumes Servoy sequences on existing tables (which may not be the case). However, if you import and check this option, everything should be fine.
sebster:
Servoy Server will honor your solution settings when you check the box which says “override sequence types to the sequence types contained in the import version”.
The default is not to do this. The default is to leave sequences alone. This has the maybe unexpected effect that when you start the repository for the first time Servoy assumes Servoy sequences on existing tables (which may not be the case). However, if you import and check this option, everything should be fine.
If it’s not in your build yet, then you should update to the latest build.
If it’s not in that build, then it will be in the next build (the next beta will be released quite soon).
However, I’m quite sure it should be available in the last beta.