This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi, We are migrating a bunch of existing data. We are thinking about using KeyTable for IDS, and just making sure after migration that the KeyTable value is higher than any migrated ID (from any table). So far, so, good, we think. But, question: do we have to make sure that our migrated IDS are unique database-wide? I ask because if LightSpeed had inserted that data, under a KeyTable regime, then they would be. When LS is using KeyTable, will it ever construct any queries that assume global uniqueness of IDs? I ask because in a very old thread Andrew wrote: "There are also some secondary gains from being able to assume that keys are database unique." http://www.mindscapehq.com/forums/thread/1016 I am hoping that these secondary gains relate only to the allocation of new IDS, and have no bearing on querying existing data - but just wanted to make sure. John |
|
|
Yep thats correct - internally uniqueness is assumed to be a combination of Type and IdValue so there is no impact of having the same Id across multiple tables.
|
|
|
Thanks. |
|