List:Commits« Previous MessageNext Message »
From:jon Date:August 14 2007 5:41am
Subject:svn commit - mysqldoc@docsrva: r7448 - trunk/refman-5.1
View as plain text  
Author: jstephens
Date: 2007-08-14 07:41:04 +0200 (Tue, 14 Aug 2007)
New Revision: 7448

Log:

Added some indexterms for ClusterRep issues...



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


Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml	2007-08-13 16:37:50 UTC (rev 7447)
+++ trunk/refman-5.1/mysql-cluster.xml	2007-08-14 05:41:04 UTC (rev 7448)
Changed blocks: 8, Lines Added: 55, Lines Deleted: 0; 4092 bytes

@@ -18893,6 +18893,11 @@
 
             <title>Loss of master-slave connection</title>
 
+            <indexterm>
+              <primary>MySQL Cluster replication</primary>
+              <secondary>loss of connection</secondary>
+            </indexterm>
+
             <para>
               Prior to MySQL 5.1.18, a MySQL Cluster replication slave
               <command>mysqld</command> had no way of detecting that the

@@ -18946,6 +18951,16 @@
 
             <title>Multi-byte character sets</title>
 
+            <indexterm>
+              <primary>MySQL Cluster replication</primary>
+              <secondary>and multi-byte character sets</secondary>
+            </indexterm>
+
+            <indexterm>
+              <primary>multi-byte character sets</primary>
+              <secondary>and MySQL Cluster (replication)</secondary>
+            </indexterm>
+
             <para>
               There are several known issues with regard to the use of
               multi-byte characters sets with MySQL Cluster Replication.

@@ -18961,6 +18976,21 @@
 
             <title>Circular replication</title>
 
+            <indexterm>
+              <primary>circular replication</primary>
+              <secondary>in MySQL Cluster</secondary>
+            </indexterm>
+
+            <indexterm>
+              <primary>replication</primary>
+              <secondary>circular</secondary>
+            </indexterm>
+
+            <indexterm>
+              <primary>MySQL Cluster replication</primary>
+              <secondary>and circular replication</secondary>
+            </indexterm>
+
             <para>
               Prior to MySQL 5.1.18, circular replication was not
               supported with MySQL Cluster replication, due to the fact

@@ -19067,6 +19097,11 @@
 
             <title>DDL statements</title>
 
+            <indexterm>
+              <primary>MySQL Cluster replication</primary>
+              <secondary>and DDL</secondary>
+            </indexterm>
+
             <para>
               The use of data definition statements, such as
               <literal>CREATE TABLE</literal>, <literal>DROP

@@ -19083,6 +19118,11 @@
 
             <title>Explicit primary key required</title>
 
+            <indexterm>
+              <primary>MySQL Cluster replication</primary>
+              <secondary>and primary key</secondary>
+            </indexterm>
+
             <para>
               In MySQL 5.1.6, only those <literal>NDB</literal> tables
               having explicit primary keys could be replicated. This

@@ -19097,6 +19137,11 @@
 
             <title>Restarting with <option>--initial</option></title>
 
+            <indexterm>
+              <primary>MySQL Cluster replication</primary>
+              <secondary>and --initial option</secondary>
+            </indexterm>
+
             <para>
               Restarting the cluster with the
               <option>&ddash;initial</option> option will cause the

@@ -19120,6 +19165,11 @@
             <title><literal>auto_increment_offset</literal> and
               <literal>auto_increment_increment</literal> variables</title>
 
+            <indexterm>
+              <primary>MySQL Cluster replication</primary>
+              <secondary>and auto_increment* variables</secondary>
+            </indexterm>
+
             <para>
               The use of the <literal>auto_increment_offset</literal>
               and <literal>auto_increment_increment</literal> server

@@ -19137,6 +19187,11 @@
 
             <title>Replication from <literal>NDB</literal> to other storage engines</title>
 
+            <indexterm>
+              <primary>MySQL Cluster replication</primary>
+              <secondary>storage engines other than NDB on slave</secondary>
+            </indexterm>
+
             <para>
               If you attempt to replicate from a MySQL Cluster to a
               slave that uses a storage engine that does not handle its


Thread
svn commit - mysqldoc@docsrva: r7448 - trunk/refman-5.1jon14 Aug