In my database I have ID columns for the primary id numbers. This is generated from a table I have designed specifically for id generation. This way my web pages and Servoy all stay in sync when creating new rows.
It would appear that with the install of Servoy 3.1X. Servoy changed all of these ID’s so that they were auto generated by Servoy. Thus throwing off my sequence. I have had to manually go in to each table inside Servoy and click on the properties and turn off the auto sequence by Servoy area. This has caused quite a headache where duplicate number were trying to be generated. Luckily MYSQL did not allow this. It could have been a very large disaster!
I would recommend that in the future, Servoy not be allowed to take over ID sequencing without permission from the developer.
I assume you had things changed to servoy sequences when you moved the solution to a new repository, right?
When you import a solution for the first time into a repository, via the admin pages, then make sure you select the checkbox “Override sequence types to the sequence types contained in the import version.”.
Only then will it keep your sequence settings.
YES, we also DO have BIG problems with that (and not only with that). When creating a database, Servoy assigns to each integer attribute a sequence, even if an entity (table) has a composite key (i. e. pk consisting of many attributes). This is just plain wrong and extremly dangerous. If you import data (now) and don’t realise the situation, you are done - I want to say your applications data are destroyed (by a big chance)!!! So that means after each creation of the whole database or part of it (i. e. one or more tables) one has to manually correct, i. e. remove the sequence assigments for each table very very carefully. This is not funny at all as this can occur quite often in the development cycle.
I have to say that I have the feeling that Servoy doesn’t take care of the problems related to the database or don’t understand them or don’t care. Sorry to say that but we already lost so many days because these things don’t work the way they should and worse, create very dangerous situation. I have to import more than 50 tables again because of this.
I agree with you that Servoy may in no way take over ID sequencing they do right now. The tool produces out of nothing a lot of work which doesn’t exist at all. And that every time we create the db again (> 120 tables).
Best regards, Robert
elyod_72:
In my database I have ID columns for the primary id numbers. This is generated from a table I have designed specifically for id generation. This way my web pages and Servoy all stay in sync when creating new rows.
It would appear that with the install of Servoy 3.1X. Servoy changed all of these ID’s so that they were auto generated by Servoy. Thus throwing off my sequence. I have had to manually go in to each table inside Servoy and click on the properties and turn off the auto sequence by Servoy area. This has caused quite a headache where duplicate number were trying to be generated. Luckily MYSQL did not allow this. It could have been a very large disaster!
I would recommend that in the future, Servoy not be allowed to take over ID sequencing without permission from the developer.
Yes Robert I totally agree with you.
And the worst part about it was that there was no warning from Servoy that this happens. It was not until my tables were trying to create duplicate id numbers because Servoy had already done it “For me” that I realized there was a problem. I had to then spend the next 4 days troubleshooting and removing problems created by Servoy generated id numbers.
If Servoy touts itself as “simply a User Interface” that can so easily hook up to any database. Then do that, and don’t automatically try to do tasks that should be handled by the back-end database.
elyod_72:
In my database I have ID columns for the primary id numbers. This is generated from a table I have designed specifically for id generation. This way my web pages and Servoy all stay in sync when creating new rows.
It would appear that with the install of Servoy 3.1X. Servoy changed all of these ID’s so that they were auto generated by Servoy. Thus throwing off my sequence. I have had to manually go in to each table inside Servoy and click on the properties and turn off the auto sequence by Servoy area. This has caused quite a headache where duplicate number were trying to be generated. Luckily MYSQL did not allow this. It could have been a very large disaster!
I would recommend that in the future, Servoy not be allowed to take over ID sequencing without permission from the developer. ?
If Servoy (server/developer) finds a table it has not seen before, it sets a servoy seq on the pk, if you change this once or say during import it allowed to override the sequnce type (from default created one to none as specified in the solution), it should work.