Re: MySQL 4.0.20 auto_increment bug

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Fred,

> No where in this documentation does it mentions what happens if someone
> re sequence the numbers. Restarting MySQL works around the problem
> because it forces the above SELECT statement (or the equivalent) to be
> called again. Another workaround would be to execute that SELECT
> statement after any re-sequencing of an auto_increment column.
>
> I am a big proponent of *expected* behavior, especially since a subtlety
> such as this could easily be missed and wind up corrupting a database.
> So I personally would consider this a bug.

We do have an existing bug report regarding this, though it also is
noted as being expected behavior for the InnoDB storage engine:

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

Currently it is considered a feature request.

Best regards,
- --
Dean Ellis, Support Engineer & Software Developer
MySQL AB, www.mysql.com

Are you MySQL certified?  http://www.mysql.com/certification
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFBEplKAebV/bGJ5NERApPoAKCIJ8GolVbmNeeFE/+MrivDf503xACeIHSF
ZnzUdwA6ZVquwFshBXdaWus=
=gTF+
-----END PGP SIGNATURE-----

-- 
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe:    http://lists.mysql.com/[email protected]