seq changed from dbidentity to servoy_seq

Classic Servoy
1

Hi there,

I have exported a solution called “mysolution” from server_a and then I imported the “mysolution” in the server_b. Before I imported the solution in the server_b, another version of “mysolution” existed in the server_b. I deleted that first and made so that there were no versions of “mysolution” anymore in the server_b.

After the import I got the following warning message. (one warning for each table in the solution)

The server version of the column ‘event_id’ of table ‘event’ in server ‘sample_solution’ has ‘servoy seq’ sequence type while the import version has ‘db identity’ sequence type.

This error seems illogical since the there is no server version of the solution “mysolution” since I deleted the old version prior to the import. Also the import version has got all the table definition with pk (dbidentity). But after the import in the server_b all the pk fields are changed to servoy_seq. I have to remember and manually change all the servoy_seq to dbidentity.

Is this a bug or am I doing something wrong?

Thanks for your help.

2

we’ve just noticed this as well; it’s causing some serious
problems at our client site (“can’t save form data”, etc.)

rm.

3

Can’t save form data occurred when servoy tries to insert a duplicate primary key id that we found out

4

is this a bug? servoy people please acknowledge. thanks a lot!

5

This problem is quit annoying. I have imported the solution into the laptop for an urgent presentation. The seq changed from db identity to servoy seq. is this a bug? please check.

Thanks!

6

see this discussion: Sequence handling on repository import - Classic Servoy - Servoy Community