MySQL Lists are EOL. Please join:

List:Commits« Previous MessageNext Message »
From:jon.stephens Date:March 17 2010 3:00pm
Subject:svn commit - mysqldoc@docsrva: r19573 - trunk/refman-5.1
View as plain text  
Author: jstephens
Date: 2010-03-17 16:00:33 +0100 (Wed, 17 Mar 2010)
New Revision: 19573

Log:

Fixes Docs BUG#52061



Modified:
   trunk/refman-5.1/mysql-cluster-replication-core.xml


Modified: trunk/refman-5.1/mysql-cluster-replication-core.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-replication-core.xml	2010-03-17 14:41:37 UTC (rev 19572)
+++ trunk/refman-5.1/mysql-cluster-replication-core.xml	2010-03-17 15:00:33 UTC (rev 19573)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 7; 1142 bytes

@@ -809,13 +809,8 @@
             ... ON DUPLICATE KEY UPDATE</literal> statements. You can
             suppress these in MySQL Cluster NDB 6.2 by using
             <option role="mysqld">--ndb-log-update-as-write=0</option>,
-            which forces all columns from updated rows to be sent (and
-            not just those that were updated). For MySQL Cluster NDB
-            6.3.3 and later, there are additional way to determine
-            whether or not an update to the row on the master should be
-            applied on the slave <command>mysqld</command>; see
-            <xref linkend="mysql-cluster-replication-conflict-resolution"/>,
-            for more information about these methods.
+            which forces updates to be logged as writes (rather than as
+            updates).
           </para>
 
         </formalpara>


Thread
svn commit - mysqldoc@docsrva: r19573 - trunk/refman-5.1jon.stephens17 Mar