Bug #11080 | Multi-row REPLACE fails on a duplicate key error on an AUTO-INC column | ||
---|---|---|---|
Submitted: | 3 Jun 2005 17:32 | Modified: | 7 Jun 2005 10:52 |
Reporter: | Heikki Tuuri | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Optimizer | Severity: | S3 (Non-critical) |
Version: | 5.0.7 | OS: | Linux (Linux/x86) |
Assigned to: | Michael Widenius | CPU Architecture: | Any |
[3 Jun 2005 17:32]
Heikki Tuuri
[3 Jun 2005 17:52]
MySQL Verification Team
Thank you for the bug report.
[6 Jun 2005 17:29]
Michael Widenius
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release. If necessary, you can access the source repository and build the latest available version, including the bugfix, yourself. More information about accessing the source trees is available at http://www.mysql.com/doc/en/Installing_source_tree.html Additional info: Fix will be in 5.0.6. Note that the fix only fixes MyISAM tables. For this to work with InnoDB tables we have to fix that InnoDB stores max used auto-increment value for UPDATES. See bug #11005 for more details regarding this
[6 Jun 2005 17:29]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/25663
[7 Jun 2005 10:39]
Heikki Tuuri
Hi! I pushed the fix to bug #11005 a few minutes ago, and it will fix also this REPLACE bug for InnoDB. But I did NOT change the InnoDB behavior in an UPDATE. It will remain different from MyISAM. The fix will probably be in 5.0.6. Regards, Heikki
[7 Jun 2005 10:52]
Heikki Tuuri
Of course I meant the fix will probably be in 5.0.7. --Heikki