DB Identity Columns which are not primary keys

Classic Servoy
1

Hi Servoy,

We have several tables which use DB Identity columns but these columns are not primary keys. This is a perfectly valid scenario in any database which supports DB Identity and as far as I know there is no requirement anywhere else to make the DB Identity columns the primary key for a table.
Why does Servoy produce a warning for these cases? What is the potential problem here?
On top of that in the preferences page developers can mark such problem markers only as Warning or Error - the options Info and Ignore are missing.

I am very curious to get your input on this. As far as I am concerned, if such problem marker exists at all, its default value should be either Ignore or Info.

2

Rossen,

There was an issue in Servoy related to a db identity column not being the pk.
This is possibly db dialect related.

Do these columns work OK for you?

Rob