From: jon.stephens
Date: February 22 2009 8:07pm
Subject: svn commit - mysqldoc@docsrva: r13884 - in trunk: refman-5.1 refman-6.0
List-Archive: http://lists.mysql.com/commits/67122
Message-Id: <200902222007.n1MK72IX026363@docsrva.mysql.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Author: jstephens
Date: 2009-02-22 21:07:02 +0100 (Sun, 22 Feb 2009)
New Revision: 13884

Log:

Noted Replication Bug #42851 as a known issue.



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	2009-02-22 19:46:38 UTC (rev 13883)
+++ trunk/refman-5.1/replication-notes.xml	2009-02-22 20:07:02 UTC (rev 13884)
Changed blocks: 1, Lines Added: 15, Lines Deleted: 6; 1906 bytes

@@ -1623,23 +1623,32 @@
         rows affected is not defined. (Such statements can be replicated
         correctly when using <literal>STATEMENT</literal> mode only if
         they also contain an <literal>ORDER BY</literal> clause.)
-        Beginning with MySQL 5.1.24, when such a statement (without
-        <literal>ORDER BY</literal>) is encountered:
+        Beginning with MySQL 5.1.24, when such a statement is
+        encountered:
 
         <itemizedlist>
 
           <listitem>
             <para>
-              when using <literal>STATEMENT</literal> mode, a warning
+              When using <literal>STATEMENT</literal> mode, a warning
               that the statement is not safe for statement-based
-              replication is now issued
+              replication is now issued.
             </para>
+
+            <para>
+              Currently, when using <literal>STATEMENT</literal> mode,
+              warnings are issued for DML statements containing
+              <literal>LIMIT</literal> even when they also have an
+              <literal>ORDER BY</literal> clause (and so are made
+              deterministic). This is a known issue which we are working
+              to resolve in a future MySQL release. (Bug #42851)
+            </para>
           </listitem>
 
           <listitem>
             <para>
-              when using <literal>MIXED</literal> mode, the statement is
-              now automatically replicated using row-based mode
+              When using <literal>MIXED</literal> mode, the statement is
+              now automatically replicated using row-based mode.
             </para>
           </listitem>
 


Modified: trunk/refman-6.0/replication-notes.xml
===================================================================
--- trunk/refman-6.0/replication-notes.xml	2009-02-22 19:46:38 UTC (rev 13883)
+++ trunk/refman-6.0/replication-notes.xml	2009-02-22 20:07:02 UTC (rev 13884)
Changed blocks: 1, Lines Added: 13, Lines Deleted: 4; 1468 bytes

@@ -1615,16 +1615,25 @@
 
           <listitem>
             <para>
-              when using <literal>STATEMENT</literal> mode, a warning
+              When using <literal>STATEMENT</literal> mode, a warning
               that the statement is not safe for statement-based
-              replication is now issued
+              replication is now issued.
             </para>
+
+            <para>
+              Currently, when using <literal>STATEMENT</literal> mode,
+              warnings are issued for DML statements containing
+              <literal>LIMIT</literal> even when they also have an
+              <literal>ORDER BY</literal> clause (and so are made
+              deterministic). This is a known issue which we are working
+              to resolve in a future MySQL release. (Bug #42851)
+            </para>
           </listitem>
 
           <listitem>
             <para>
-              when using <literal>MIXED</literal> mode, the statement is
-              now automatically replicated using row-based mode
+              When using <literal>MIXED</literal> mode, the statement is
+              now automatically replicated using row-based mode.
             </para>
           </listitem>