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.
Yep, we are of similar minds on this. To me SIGNED/UNSIGNED is
really just a constraint anyways.
It would get rid of the val_int/val_uint mess and special case
casting etc that mysql has right now.
This is on the list.
The proposal I first have for Field is the class break up of the
files. I've mentioned this on IRC, and I think I have mentioned it
here as well. Next week my focus will be more on install/cleanup.
After that this is something I either want to tackle or see someone
else tackle.
All in time :)
Cheers,
-Brian
--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/ <-- Me
http://tangent.org/ <-- Software
_______________________________________________________
You can't grep a dead tree.
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
