Is it safe to execute INSERT sql’s in the database for deploying preloaded data? We are using “servoy seq” as our Sequence process in our primary key. I just noticed that “Next value” in “Servoy Sequence” Tab has a conflicting value with the deployed database’s primary keys. Does Servoy has a main lookup table for all the primary key sequencing? If Servoy has this, the INSERT SQL file would just update the lookup table to a new “Next Value” so that no conflicting primary keys would arise in the future.
The best practise is to use dbidentity or dbsequence in Servoy when accessing the database also outside Servoy.
In case you want to keep servoy sequences and insert SQL outside Servoy, you have to sync the servoy sequences via “Update servoy seq for all tables” on a database server in the admin page.
Jan Blok:
The best practise is to use dbidentity or dbsequence in Servoy when accessing the database also outside Servoy.
In case you want to keep servoy sequences and insert SQL outside Servoy, you have to sync the servoy sequences via “Update servoy seq for all tables” on a database server in the admin page.
Will there be any conflict if we have our own table for sequences when generating primary keys?
Not sure if I understand your question, but the idea with identity/dbseq is that a central (db managed )place holds the sequence info. (for all applications using the database)