Author: mcbrown
Date: 2007-02-07 11:46:17 +0100 (Wed, 07 Feb 2007)
New Revision: 4838
Log:
Fixing ID to replication-row-based to the new replication-formats ID
Modified:
trunk/refman-5.1/database-administration.xml
trunk/refman-5.1/faqs.xml
trunk/refman-5.1/introduction.xml
trunk/refman-5.1/mysql-cluster.xml
trunk/refman-5.1/news-5.1.xml
trunk/refman-5.1/stored-procedures.xml
Modified: trunk/refman-5.1/database-administration.xml
===================================================================
--- trunk/refman-5.1/database-administration.xml 2007-02-07 10:41:47 UTC (rev 4837)
+++ trunk/refman-5.1/database-administration.xml 2007-02-07 10:46:17 UTC (rev 4838)
Changed blocks: 4, Lines Added: 4, Lines Deleted: 4; 2075 bytes
@@ -680,7 +680,7 @@
<para>
Specify whether to use row-based or statement-based
replication (statement-based is default). See
- <xref linkend="replication-row-based"/>. This option was
+ <xref linkend="replication-formats"/>. This option was
added in MySQL 5.1.5.
</para>
</listitem>
@@ -705,7 +705,7 @@
in bytes. Rows are grouped into events smaller than this
size if possible. The value should be a multiple of 256.
The default is 1024. See
- <xref linkend="replication-row-based"/>. This option was
+ <xref linkend="replication-formats"/>. This option was
added in MySQL 5.1.5.
</para>
</listitem>
@@ -3643,7 +3643,7 @@
startup, or by the <literal>binlog_format</literal>
variable at runtime (you need the <literal>SUPER</literal>
privilege to set this variable on a global scope). See
- <xref linkend="replication-row-based"/>. The startup
+ <xref linkend="replication-formats"/>. The startup
variable was added in MySQL 5.1.5, and the runtime
variable in MySQL 5.1.8. <literal>MIXED</literal> was
added in MySQL 5.1.8.
@@ -4602,7 +4602,7 @@
replication using row-based binary logging. If the value
is <literal>NO</literal>, the server can use only
statement-based logging. See
- <xref linkend="replication-row-based"/>. This variable was
+ <xref linkend="replication-formats"/>. This variable was
added in MySQL 5.1.5. This variable was removed in 5.1.15.
</para>
</listitem>
Modified: trunk/refman-5.1/faqs.xml
===================================================================
--- trunk/refman-5.1/faqs.xml 2007-02-07 10:41:47 UTC (rev 4837)
+++ trunk/refman-5.1/faqs.xml 2007-02-07 10:46:17 UTC (rev 4838)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 454 bytes
@@ -1689,7 +1689,7 @@
<para>
For additional information, see
- <xref linkend="replication-row-based"/>.
+ <xref linkend="replication-formats"/>.
</para>
</answer>
Modified: trunk/refman-5.1/introduction.xml
===================================================================
--- trunk/refman-5.1/introduction.xml 2007-02-07 10:41:47 UTC (rev 4837)
+++ trunk/refman-5.1/introduction.xml 2007-02-07 10:46:17 UTC (rev 4838)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 695 bytes
@@ -419,7 +419,7 @@
is available: <emphasis>mixed</emphasis>. This will use
statement-based replication by default, and only switch to
row-based replication in particular cases. See
- <xref linkend="replication-row-based"/>. (Authors: Lars
+ <xref linkend="replication-formats"/>. (Authors: Lars
Thalmann, Guilhem Bichot, Mats Kindahl)
</para>
</listitem>
Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml 2007-02-07 10:41:47 UTC (rev 4837)
+++ trunk/refman-5.1/mysql-cluster.xml 2007-02-07 10:46:17 UTC (rev 4838)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1149 bytes
@@ -15341,7 +15341,7 @@
with <option>--binlog-format=row</option>, as described in
<xref linkend="mysql-cluster-replication-starting"/>. For
general information about row-based replication, see
- <xref linkend="replication-row-based"/>.
+ <xref linkend="replication-formats"/>.
</para>
<para>
@@ -15905,7 +15905,7 @@
Ensure that each MySQL server acting as a replication master
is configured with a unique server ID, and with binary
logging enabled, using the row format. (See
- <xref linkend="replication-row-based"/>.) These options can
+ <xref linkend="replication-formats"/>.) These options can
be set either in the master server's
<filename>my.cnf</filename> file, or on the command line
when starting the master <command>mysqld</command> process.
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-02-07 10:41:47 UTC (rev 4837)
+++ trunk/refman-5.1/news-5.1.xml 2007-02-07 10:46:17 UTC (rev 4838)
Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 1140 bytes
@@ -11309,7 +11309,7 @@
The <literal>binlog_format</literal> system variable now is
dynamic and can be changed at runtime, as described in
<xref
- linkend="replication-row-based"/>.
+ linkend="replication-formats"/>.
</para>
</listitem>
@@ -11319,7 +11319,7 @@
be set to a third format, <literal>MIXED</literal>, as
described in
<xref
- linkend="replication-row-based"/>.
+ linkend="replication-formats"/>.
</para>
</listitem>
@@ -13938,7 +13938,7 @@
binary logging. Added the <option>--binlog-format</option> and
<option>--binlog-row-event-max-size</option> server options
for binary logging control. See
- <xref linkend="replication-row-based"/>.
+ <xref linkend="replication-formats"/>.
</para>
</listitem>
Modified: trunk/refman-5.1/stored-procedures.xml
===================================================================
--- trunk/refman-5.1/stored-procedures.xml 2007-02-07 10:41:47 UTC (rev 4837)
+++ trunk/refman-5.1/stored-procedures.xml 2007-02-07 10:46:17 UTC (rev 4838)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 662 bytes
@@ -2241,7 +2241,7 @@
occurs at the SQL statement level. If you use row-based binary
logging, the log contains changes made to individual rows as a
result of executing SQL statements. For general information about
- row-based logging, see <xref linkend="replication-row-based"/>.
+ row-based logging, see <xref linkend="replication-formats"/>.
</para>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r4838 - trunk/refman-5.1 | mcbrown | 7 Feb |
