Speaking somewhat from ignorance here, but
It would be nice if was possible for the db server to delegate
(possibly optionally), all handling of auto incremement and auto
unique keys to the storage engine.
That was one of the challenges facing IBM with the DB2 storage engine,
was that the auto increment keys are handled on the System i db2
layer, not in the AIX VM that the MySQL instance was running in, and
keeping MySQL's idea of what the next value was and keeping the DB2
process's idea of what the next value was, was challenging.
On Feb 4, 2009, at 2:22 PM, Brian Aker wrote:
Hi!
Auto-increments have always had a set behavior... some of this
worked well, and some of it causes bottlenecks.
1) They always increase in value in the table. You can use them as a
"what came before what".
2) Gaps don't (for the most part) exist).
What are people's feelings about the above assumptions? Is it ok to
break them, or would it be better to add a different type which did
not have the above assumptions, and leave the old ones in?
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
--
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
