We ship out mySQL on our appliances in enterprise level scenarios. We
often
like to start the AUTO_INCREMENT for several tables at 10,000 -- this way
we
can reserve the lower 'block' of IDs for our own internal and 'default'
use
so all customers have the same basic database schema. It also
http://dev.mysql.com/doc/refman/5.0/en/innodb-auto-increment-column.html
We have recently switched several database tables from MYISM to INNODB, only
to find out this colossal design flaw in InnoDB tables.
We ship out mySQL on our appliances in enterprise level scenarios. We often
like to start
I came up with a work around when we encountered this. I don't remember
exactly (and I don't have access to that code anymore), but I think we
manually put a piece of code in our SQL setup scripts, before any of our
insert statements. This 'mysql command' would set the next available ID
to
Daevid,
That page looks a little misleading.
First, it says it's stored in main memory, not on disk.
Then it says that on server-startup, it finds the largest value in the
table, and initialized it to that. So it is disk-based on startup, and
then resides in memory thereafter.
This doesn't
