Information générale
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
I was suprised there is no FAQ in this section for the proper (or best practice) method of generating unique primary keys.
I was wondering what the pro/con to the following would be:
Data-based: Concatenate enough data to be reliably sure of a unique index
MachineName+SomeDatetime value: The machine putting the data into the table stamps record with it's name and current datetime (which would need to be accurate to a very small interval for multiple fast inserts)
KeyGenerator: a separate mechanism for creating keys (like a next-highest-value field in a key table)
I'm currently using a view with update keys on location/repID/project, but i learned after the first implementation that this app will require the ability to change the repID from the edit grid. I would have preferred this information be part of the initial design specs, but since it wasn't - i'd like to only fix this issue once, with the best update key strategy possible.
thanks
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement