Author: jstephens
Date: 2008-03-07 15:10:47 +0100 (Fri, 07 Mar 2008)
New Revision: 10155
Log:
Fix for Docs Bug #35135
Modified:
trunk/refman-5.1/replication-notes.xml
trunk/refman-6.0/replication-notes.xml
Modified: trunk/refman-5.1/replication-notes.xml
===================================================================
--- trunk/refman-5.1/replication-notes.xml 2008-03-07 13:24:27 UTC (rev 10154)
+++ trunk/refman-5.1/replication-notes.xml 2008-03-07 14:10:47 UTC (rev 10155)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 3; 873 bytes
@@ -98,10 +98,11 @@
</para>
<para>
- When a trigger causes an <literal>INSERT</literal> into an
+ Prior to MySQL 5.1.12, when a trigger caused an
+ <literal>INSERT</literal> into an
<literal>AUTO_INCREMENT</literal> column, the generated
- <literal>AUTO_INCREMENT</literal> value is not written into the
- binary log, so a different value can in some cases be inserted
+ <literal>AUTO_INCREMENT</literal> value was not written into the
+ binary log, so a different value could in some cases be inserted
on the slave.
</para>
Modified: trunk/refman-6.0/replication-notes.xml
===================================================================
--- trunk/refman-6.0/replication-notes.xml 2008-03-07 13:24:27 UTC (rev 10154)
+++ trunk/refman-6.0/replication-notes.xml 2008-03-07 14:10:47 UTC (rev 10155)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 8; 852 bytes
@@ -91,14 +91,6 @@
</para>
<para>
- When a trigger causes an <literal>INSERT</literal> into an
- <literal>AUTO_INCREMENT</literal> column, the generated
- <literal>AUTO_INCREMENT</literal> value is not written into the
- binary log, so a different value can in some cases be inserted
- on the slave.
- </para>
-
- <para>
Adding an <literal>AUTO_INCREMENT</literal> column to a table
with <literal>ALTER TABLE</literal> might not produce the same
ordering of the rows on the slave and the master. This occurs
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r10155 - in trunk: refman-5.1 refman-6.0 | jon | 7 Mar |
