I was thinking of using a single db table with single db column to store
the current 'highest value' for the primary key.

If anyone's used this method before...do you this incremental value
across multiple tables? i.e. I have a table for 'orders' and another for
'users'. Would both feed off this single primary key table?

Any downsides to this? I need to avoid the use of any triggers or stored
procs in this project. I'm so tempted to just use UUIDs...but the amount
of data can potentially grow quite large and I'm a little worried about
the join performance with UUIDs.

Any opinions appreciated

Stace

AVIS IMPORTANT:
-------------------------------
Les informations contenues dans le present document et ses pieces jointes sont strictement confidentielles et reservees a l'usage de la (des) personne(s) a qui il est adresse. Si vous n'etes pas le destinataire, soyez avise que toute divulgation, distribution, copie, ou autre utilisation de ces informations est strictement prohibee. Si vous avez recu ce document par erreur, veuillez s'il vous plait communiquer immediatement avec l'expediteur et detruire ce document sans en faire de copie sous quelque forme.

WARNING:
-------------------------------
The information contained in this document and attachments is confidential and intended only for the person(s) named above. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution, or any other use of the information is strictly prohibited. If you have received this document by mistake, please notify the sender immediately and destroy this document and attachments without making any copy of any kind.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to