Weaknesses of UUIDs:
long, non-integer values = slower as keys in some DBs
possibly not unique if generated in quick succession (time element is not
very granular)
Not that MAX() is perfect. In very-high-insert environments people
sometimes generate random ID's, catching and trying again the few that
collide with existing values; the theory is that the insert activity is then
spread around the table (physically), avoiding a "hot spot" with lots of
write contention. May only work in multiprocessor DBMS systems.
-----Original Message-----
From: Leyne, Sean [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 25, 2000 9:45 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Avoiding using the MAX function
Nick,
Agreeing with you completely regarding the overhead of a DB call.
I find it very interesting that people don't recommend the use of UUID
as DB keys. In this way, using CreateUUID, CF would already know the
key value and the DB INSERT would proceed on it's own.
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
