Servoy still doesn’t honer database sequences ‘out of the box’ (PostgreSQL).
You have to set them manually and when you import the solution into another server you have to do the same routine again(!).
When you force Servoy to read the sequence names from the database it still doesn’t get it right (seq_… instead of …_seq)
Servoy fills null values in columns that have default values defined on the database level. Rendering them useless (PostgreSQL).
Records with FK’s that have a NULL value suddenly relate to every record in the related table (!).
This is all reported before but no response from the dev team so far on the last 2 issues.
Surprisingly little response at all to the reported issues of this specific build actually.
ROCLASI:
This is all reported before but no response from the dev team so far on the last 2 issues.
Surprisingly little response at all to the reported issues of this specific build actually.
No response does not mean that we are not looking into it. Particularly with beta versions it is hard to reply to each and every notice of a bug. Rest assured that we are working on all issues mentioned.
Servoy should honor database sequences on import. In the admin pages there is an option allowing you to override existing sequences and use the versions from the import. In the developer, if the versions in the import and database do not match, Servoy asks which one you wish to use. If this does not work for you, then something is wrong, and I definately need more information to find the source of the problem so we can fix it.
With a database sequence (not db identity), there is no way for servoy to know which sequence should be used for a column. (In fact, there is no way to know.)
The other issue (database defaults) will be looked into by Johan.
as you know, sequence handling is also my favourite
I have made a feature request regarding this statement
With a database sequence (not db identity), there is no way for servoy to know which sequence should be used for a column. (In fact, there is no way to know.)
I think it would be VERY helpful if we could default the sequence name to table + ‘_seq’. Since in most of our solutions we have control over the database, couldn’t this be done? If there is a possibility to manually override a default sequence name, it’d be perfect on databases that support db identities AND databases that (only) support sequences like ORACLE.