Hi,
I noticed there's a lot of discussion dating back to 2005 about the use of auto_increment in drupal and modules.
If I understand correctly, the drupal core uses sequences through db_next_id() to get the number for the next key.
However, the mysql database created by Drupal has auto_increment setup for most id's, including the node table.
Why does a node have auto_increment if the code uses db_next_id() anyway? The risk is that if for some reason a node
gets inserted without the use of db_next_id(), mysql will figure out the next id, which causes the sequence table to be
out of sync.
So I'd figure it's safer to remove auto_increment from all the core tables.
The reason I stumbled on this is that we migrated an existing drupal setup and got duplicate key problems in the
node table at some point (the fix is to manually change the highest number in the sequence table as somebody
suggested earlier).
Btw we're using mysql 5 with master/slave replication and the php connections get loadbalanced on two nodes.
Drupal only connects to the master db so the replication shouldn't be a problem...
Ricardo.
