On Jul 12, 2008, at 1:41 PM, Brian Aker wrote:
Hi!
On Jul 12, 2008, at 1:27 PM, Antony T Curtis wrote:
UUID generation must be made good. It would be very useful for
people in multi-master situation where they can have a column
declared as:
my_id HUGEINT NOT NULL PRIMARY KEY AUTO_UUID,
Where AUTO_UUID is an alternative to AUTO_INCREMENT and the UUID
would be returned in LAST_INDEX_ID() as expected. Then no need to
worry about sharding the primary key: It should be very unlikely
for pk collision.
Why not just declare UUID a type like timestamp() which just fills
itself? Declaring it primary key is gravy (though for Innodb and
similar engines this has positives/negatives).
Right now I want to see the generation improved upon. The current
global lock is an issue. My current feeling is to toss it if it is
tree Ted's library is better.
I suspect the global lock is there either because the UUID generator
isnt reentrant, or that it has "is this REALLY unique?" test
Make it reentrant, and trust that it will be unique, and make it
lockless.
--
Mark Atwood <http://mark.atwood.name>
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
