Create a table called “template” with an id field set to Servoy sequence.
Copy the table, with “copy column properties” checked.
New table has servoy sequence. Add a few records in a dummy form and you’ll see that it really is sequencing.
Restart servoy.
Key is no longer servoy sequenced. New records have a blank id, and the second one of those will give you a “non-unique key” error that requires a lot of restarting apps and databases and generally fumbling around (at least for me) before you can get any part of the solution to work again.
Not hard to work around now that I see it happen, but this cost me about five hours of banging my head against the wall, trying to figure out how I was getting non-unique keys, and then trying to figure out why earlier records (before reset) had valid id’s, but later records didn’t.
Actually, feeling much better now that I’ve figured out how it happened.
I just created seven new tables by copying my ‘template’ table. Restarted servoy. Servoy seq no longer set on the id field. At least now I expect it and deal with it.
Am I really the only one this is happening to? Can anyone else reproduce this?
If not, what could possibly be the difference in my setup that would cause the table to copy, but not the servoy seq… or even more peculiar, to copy it in the current session, but then lose that property on restart?
I know I ask more than my share of newbie questions , but I assure you that this is rock-solid consistent. If it’s not a bug for anyone else, then I’m concerned about the setup of my development environment.
Perhaps if we go back a step? This template table was originally part of another solution. Perhaps the error originated because the template table was copied from solution to solution?
I cannot confirm this issue. I did exactly what you did and the sequence was remembered. Funny thing though in my case: I create seven records, sequence went to 7, restarted Servoy and the next record started with sequence 16?!
my $.02- I created a copy of a table, verified that id field was set to servoy sequence, created 7 records in the new table, restarted Servoy and found that servoy seq was TURNED OFF. I turned it back on and added a new record and the id field jumped to 16 as well.!
Upon further testing, I have not been able to re-create the servoy sequence bug, however, in all cases, when I copy a table all of the properties of the new table are NOT retained upon restart. The properties are set from the Copy Table buttin action, but are lost when you re-start Developer.
Note however that if you use a database sequence on a column and copy it, the copied column will use a Servoy Sequence since Servoy cannot create database sequences itself.
Furthermore, about the jump in sequences, that happens when you use a Servoy Sequence. In fact, it can happen with any sequence, because somebody may ask for the next sequence number and not actually use it. So NEVER count on autogenerated sequences to be sequential. The reason that Servoy Sequences differ when you restart Servoy Developer is that Servoy takes sequences in blocks of about 10 at a time to minimize database access. Thus if you don’t use all of them and restart, you’ll have a gap.
since Servoy cannot create database sequences itself.
On MS SQL, it does exactly that. If I create a table and set the sequence to db identity, I do have a sequence on that column in the database? What am I getting wrong?
Database sequence: i.e., a different seperate sequence to which you have to specify the name, called db seq in Servoy developer. This is NOT created automatically.
Database identity: i.e., an autoincrement column, no named sequence has to be made, this one CAN be made by Servoy…
You probably created the second one automatically.