MySQL Bugs: #16828: mysqldump excludes auto_increment with --compatible=mysql323

Bug #16828	mysqldump excludes auto_increment with --compatible=mysql323
Submitted:	27 Jan 2006 7:12	Modified:	27 Jan 2006 11:07
Reporter:	David Pfender	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	5.0.15	OS:	Windows (win32 (ia32))
Assigned to:		CPU Architecture:	Any

Description:
When using mysqldump with the option --compatible=mysql323 (no other options) to dump an entire database (16 tables), all 6 tables that have a fields defined as
id_xx int unsigned not null auto_increment primary key;
do not have the "auto_increment" attribute in the CREATE TABLE statement.

When not using this option, the attribute is correct.  This is a serious problem trying to transfer between servers running different versions of mysql.  Everything seems to work fine until a new record is inserted and the primary key becomes 0 when it should be incremented from the previously created value.

How to repeat:
Use mysqldump with and without the single option and see the difference between the two create table statements.

Thank you for the bug report. Duplicate of bug:

http://bugs.mysql.com/bug.php?id=14515