From: jon
Date: November 4 2007 9:24am
Subject: svn commit - mysqldoc@docsrva: r8526 - in trunk: refman-5.0 refman-5.1 refman-6.0
List-Archive: http://lists.mysql.com/commits/37059
Message-Id: <200711040924.lA49O6UQ032118@docsrva.mysql.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Author: jstephens
Date: 2007-11-04 10:24:06 +0100 (Sun, 04 Nov 2007)
New Revision: 8526

Log:

Replication + trigger that does insert into an AUTO_INCREMENT = 
potential suffering

(Leith)



Modified:
   trunk/refman-5.0/replication-notes.xml
   trunk/refman-5.1/replication-notes.xml
   trunk/refman-6.0/replication-notes.xml


Modified: trunk/refman-5.0/replication-notes.xml
===================================================================
--- trunk/refman-5.0/replication-notes.xml	2007-11-04 02:04:16 UTC (rev 8525)
+++ trunk/refman-5.0/replication-notes.xml	2007-11-04 09:24:06 UTC (rev 8526)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 1; 753 bytes

@@ -110,7 +110,9 @@
             <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.
+            inserted on the slave. This is also true of a trigger that
+            causes an <literal>INSERT</literal> into an
+            <literal>AUTO_INCREMENT</literal> column.
           </para>
         </listitem>
 


Modified: trunk/refman-5.1/replication-notes.xml
===================================================================
--- trunk/refman-5.1/replication-notes.xml	2007-11-04 02:04:16 UTC (rev 8525)
+++ trunk/refman-5.1/replication-notes.xml	2007-11-04 09:24:06 UTC (rev 8526)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 0; 850 bytes

@@ -96,6 +96,14 @@
       </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


Modified: trunk/refman-6.0/replication-notes.xml
===================================================================
--- trunk/refman-6.0/replication-notes.xml	2007-11-04 02:04:16 UTC (rev 8525)
+++ trunk/refman-6.0/replication-notes.xml	2007-11-04 09:24:06 UTC (rev 8526)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 0; 850 bytes

@@ -90,6 +90,14 @@
       </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