Hi
I think most of you are missing the point here.
GUIDs are unique and they are required for Enterprise development.
For those of you who have used multi master replication on Oracle or MS
SQL, you know that identity columns and sequences are problematic. The
only way to work with primary key
Hi
The overhead in generating GUIDs is minimal.
I've never heard of a GUID implementation that uses random numbers. In
most cases it is a functions of the date, a sequence, and/or the MAC.
Why would you want to use two columns when you use could one? Two
columns in each table would clutter your
