Updating a solution

Classic Servoy
1

Is there a reason whilst updating a solution the sequence type of a column is not updated?

[warning] Did not override the sequence information of the column 'aktiv_2_medew_id' of table 'aktiv_2_medew' in server 'assyst'. 
```I changed the sequence information from servoy seq to db identity

We have decided that we would let Sybase do the autoicrementing of the pk's of all the tables after reading some forum-articles in here.
2

tweetie:
Is there a reason whilst updating a solution the sequence type of a column is not updated?

[warning] Did not override the sequence information of the column 'aktiv_2_medew_id' of table 'aktiv_2_medew' in server 'assyst'. 
```I changed the sequence information from servoy seq to db identity

We have decided that we would let Sybase do the autoicrementing of the pk's of all the tables after reading some forum-articles in here.

Just guessing: is the column set to auto-increment?
I’m not sure Servoy can understand that, but it could be a possible cause.

3

At first…I forgot to select
Override sequence types to the sequence types contained in the import version
So I set all pk’s in the Sybase to autoincrement
and selected the Override sequence etc…but now I get ```
The import version of the column ‘mv_id’ of table ‘mv’ in server ‘assyst’ has ‘db identity’ sequence type but the table already exists so it cannot be created, using ‘servoy seq’ sequence type instead.


Servoy Developer
Version R2 2.2.5-build 337
Java version 1.5.0_06-b05 (Windows 2000)
4

We are running MS SQL Server backend and have the exact same problem. It has rather strang behavior and I have had trouble providing the Servoy team with a reproducible example of the problem. Do you have a reproducible example you can provide them?

John McCann

5

Have seen this one before, and I use PostgreSQL.

The import version of the column 'mv_id' of table 'mv' in server 'assyst' has 'db identity' sequence type but the table already exists so it cannot be created, using 'servoy seq' sequence type instead.

Always restart developer or server after modifying the database using external tools.

6

Add a “Primary Key Constraint” to the pk field. This way Servoy understands that it is a pk.

7

Or delete the solution completely from the repository and import it again WITH that checkbox checked.

8

swingman:
Add a “Primary Key Constraint” to the pk field. This way Servoy understands that it is a pk.

They did have a PK constraint.

roclasi:
Or delete the solution completely from the repository and import it again WITH that checkbox checked.

Gonna try that.