Author: jstephens
Date: 2007-10-16 16:42:23 +0200 (Tue, 16 Oct 2007)
New Revision: 8116
Log:
Why an NDB table being replicated should have a primary key (Tomas)
Modified:
trunk/refman-5.1/mysql-cluster-replication.xml
trunk/refman-5.2/mysql-cluster-replication.xml
Modified: trunk/refman-5.1/mysql-cluster-replication.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-replication.xml 2007-10-16 12:17:35 UTC (rev 8115)
+++ trunk/refman-5.1/mysql-cluster-replication.xml 2007-10-16 14:42:23 UTC (rev 8116)
Changed blocks: 2, Lines Added: 8, Lines Deleted: 2; 1256 bytes
@@ -480,7 +480,7 @@
<listitem>
<formalpara>
- <title>Explicit primary key required</title>
+ <title>Cluster replication and primary keys</title>
<indexterm>
<primary>MySQL Cluster replication</primary>
@@ -490,7 +490,13 @@
<para>
In MySQL 5.1.6, only those <literal>NDB</literal> tables
having explicit primary keys could be replicated. This
- limitation was lifted in MySQL 5.1.7.
+ limitation was lifted in MySQL 5.1.7. However, in the event
+ of a node failure, errors in replication of
+ <literal>NDB</literal> tables without primary keys can still
+ occur, due to the possibility of duplicate rows being
+ inserted in such cases. For this reason, it is highly
+ recommended that all <literal>NDB</literal> tables being
+ replicated have primary keys.
</para>
</formalpara>
Modified: trunk/refman-5.2/mysql-cluster-replication.xml
===================================================================
--- trunk/refman-5.2/mysql-cluster-replication.xml 2007-10-16 12:17:35 UTC (rev 8115)
+++ trunk/refman-5.2/mysql-cluster-replication.xml 2007-10-16 14:42:23 UTC (rev 8116)
Changed blocks: 2, Lines Added: 7, Lines Deleted: 4; 1215 bytes
@@ -510,7 +510,7 @@
<listitem>
<formalpara>
- <title>Explicit primary key required</title>
+ <title>Cluster replication and primary keys</title>
<indexterm>
<primary>MySQL Cluster replication</primary>
@@ -518,9 +518,12 @@
</indexterm>
<para>
- In MySQL 5.1.6, only those <literal>NDB</literal> tables
- having explicit primary keys could be replicated. This
- limitation was lifted in MySQL 5.1.7.
+ In the event of a node failure, errors in replication of
+ <literal>NDB</literal> tables without primary keys can
+ occur, due to the possibility of duplicate rows being
+ inserted in such cases. For this reason, it is highly
+ recommended that all <literal>NDB</literal> tables being
+ replicated have primary keys.
</para>
</formalpara>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r8116 - in trunk: refman-5.1 refman-5.2 | jon | 16 Oct |