| Subject | HOW TO MANAGE ROW KEYS WHEN MOVING PROJECT FROM ONE DB TO ANOTHER? |
|---|---|
| Author | mlq97 |
| Post date | 2009-05-28T00:41:06Z |
Say I have an INVOICE table with a related LINEITEM table. The Lineitems reference the Invoice through a foreign key.
I would like to be able to freely move invoices and their related lineitems from a source DB to a target DB and back again, either as copies or for archiving purposes to reduce the size of the original DB. I would also like the target DB to be able to have data added in some other way, by other people, perhaps at a different site.
However the row keys as generated by Firebird are not globally unique, so it is theoretically possible that a source DB row ID may already exist in the target DB.
How would one normally deal with this problem? Presumably one must always use globally unique keys, but can these be generated in firebird?
Many thanks
Mitch
I would like to be able to freely move invoices and their related lineitems from a source DB to a target DB and back again, either as copies or for archiving purposes to reduce the size of the original DB. I would also like the target DB to be able to have data added in some other way, by other people, perhaps at a different site.
However the row keys as generated by Firebird are not globally unique, so it is theoretically possible that a source DB row ID may already exist in the target DB.
How would one normally deal with this problem? Presumably one must always use globally unique keys, but can these be generated in firebird?
Many thanks
Mitch