Subject | Primary keys not declared as NOT NULL |
---|---|
Author | Maya Opperman |
Post date | 2013-07-01T08:50:07Z |
Hi,
In have a Firebird 1.5 database, which somehow does not have NOT NULL ticked for the primary key field of a few tables.
When I restore the database on Firebird 2.5, it just silently drops the primary keys.
I have found and corrected 2, but suspect there may be more, which could cause some nasty headaches further down the line.
Is there any way I can see which primary keys were problematic, and therefore dropped?
I have checked the verbose restore log (no errors or warnings shown, I have tried validating the database using FB2.5 and the old ODS structure, and I have tried checking the Firebird.log.
The only thing left I can think of will be to try write a sql statement to run on the old database, to extract all primary keys that don't have a not null constraint, but that is going to take the rest of the day to get right.
Any better ideas?
Thanks
Maya
[Non-text portions of this message have been removed]
In have a Firebird 1.5 database, which somehow does not have NOT NULL ticked for the primary key field of a few tables.
When I restore the database on Firebird 2.5, it just silently drops the primary keys.
I have found and corrected 2, but suspect there may be more, which could cause some nasty headaches further down the line.
Is there any way I can see which primary keys were problematic, and therefore dropped?
I have checked the verbose restore log (no errors or warnings shown, I have tried validating the database using FB2.5 and the old ODS structure, and I have tried checking the Firebird.log.
The only thing left I can think of will be to try write a sql statement to run on the old database, to extract all primary keys that don't have a not null constraint, but that is going to take the rest of the day to get right.
Any better ideas?
Thanks
Maya
[Non-text portions of this message have been removed]