On Feb 16, 2009, at 10:14 AM, Monty Taylor wrote:
Mark Atwood wrote:
On Feb 4, 2009, at 3:04 PM, Francesco wrote:
I do find the monotonic behaviour of auto-increment useful, not from
applications but when mining the data in a client
Couldnt we get that, only better, by having a fast timestamp field?
It would make so much sense and make so much possible to just have
every
row always get a guid and highrez timestamp on creation.
Except for the extra size overhead in that.
-100 for any automatic-added-to-any-row stuff
But it would make replication so *easy*.
Maybe a sync magic type? Or a native UUID and native highrez
timestamp type, and have replication just magically know to use them
if they are defined for a table?
--
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
