I have been using MySQL for ecommerce work for quite some time. One
problem that just recently arose was a duplicate key error during db
restoration. The culprit lies in a table which has an
auto_incremented, not null defined integer field called "id". There
is an entry which was adjusted, by me, to have an "id" of 0 (instead
of 1). When mysql attempts to restore this table, after a backup, it
complains that the entry (which previously had the "id" of 0) now has
an "id" of 72, and is invalid as there already is an entry with an id
of 72.
Basically it seems that restore cannot allow for a zero value, if the
field is an auto_incremented, not null primary key. This seems like
a serious problem, since many ecommerce table designs use a zero
value in such a table to represent a catalog base.
Is there any solution in mysql?
Michael
SCWD
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
