Bug #35135 | 5.1 document incorrect about binlog in trigger generated AUTO_INCREMENT | ||
---|---|---|---|
Submitted: | 7 Mar 2008 6:48 | Modified: | 10 Mar 2008 17:13 |
Reporter: | Zhenxing He | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 5.1+ | OS: | Any |
Assigned to: | Jon Stephens | CPU Architecture: | Any |
Tags: | auto_increment, binlog |
[7 Mar 2008 6:48]
Zhenxing He
[7 Mar 2008 6:53]
Jon Stephens
Assigning to myself for investigation/resolution.
[7 Mar 2008 14:25]
Jon Stephens
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.
[10 Mar 2008 14:31]
Zhenxing He
.... Prior to MySQL 5.1.12, when a trigger caused an INSERT into an AUTO_INCREMENT column, the generated AUTO_INCREMENT value was not written into the binary log, so a different value could in some cases be inserted on the slave. ... This applies to functions too, so we should replace 'a trigger' with ' a trigger or a function' in the above text.
[10 Mar 2008 17:13]
Jon Stephens
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.