Brian Aker wrote:
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).
"no gaps" doesn't work with MVCC anyway, rollbacks cause gaps
and for MySQL Cluster even "what came before what" isn't true
anymore if you use more than one mysql node and have a
ndb_autoincrement_prefetch > 1 ...
So 2) is broken on a regular basis anyway, breaking 1) comes
as a surprices though ... and violates the very meaning of
increment: "an increase of some amount, either fixed or variable"
Something that breaks 1), like current autoincrement in cluster,
should IMHO better use a different name, e.g. auto_unique or so
--
Hartmut Holzgraefe, MySQL Regional Support Manager, EMEA
Sun Microsystems GmbH, Sonnenallee 1, 85551 Kirchheim-Heimstetten
Amtsgericht Muenchen: HRB161028
Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Dr. Roland Boemer
Vorsitzender des Aufsichtsrates: Martin Haering
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
