Author: jstephens
Date: 2010-09-17 19:27:00 +0200 (Fri, 17 Sep 2010)
New Revision: 22763
Log:
Fixes Docs BUG#56366
Modified:
trunk/refman-5.1/replication-options-core.xml
trunk/refman-5.5/replication-options-core.xml
trunk/refman-5.6/replication-options-core.xml
trunk/refman-6.0/replication-options-core.xml
Modified: trunk/refman-5.1/replication-options-core.xml
===================================================================
--- trunk/refman-5.1/replication-options-core.xml 2010-09-17 16:39:01 UTC (rev 22762)
+++ trunk/refman-5.1/replication-options-core.xml 2010-09-17 17:27:00 UTC (rev 22763)
Changed blocks: 2, Lines Added: 20, Lines Deleted: 0; 2046 bytes
@@ -2874,6 +2874,16 @@
same way that the effects of
<option role="mysqld">--replicate-do-db</option> depend on
whether statement-based or row-based replication is in use.
+ You should keep in mind that the format used to log a given
+ statement may not necessarily be the same as that indicated by
+ the value of <literal role="sysvar">binlog_format</literal>.
+ For example, DDL statements such as
+ <literal role="stmt">CREATE TABLE</literal> and
+ <literal role="stmt">ALTER TABLE</literal> are always logged
+ as statements, without regard to the logging format in effect,
+ so the following statement-based rules for
+ <option>--binlog-do-db</option> always apply in determining
+ whether or not the statement is logged.
</para>
<formalpara>
@@ -3038,6 +3048,16 @@
same way that the effects of
<option role="mysqld">--replicate-ignore-db</option> depend on
whether statement-based or row-based replication is in use.
+ You should keep in mind that the format used to log a given
+ statement may not necessarily be the same as that indicated by
+ the value of <literal role="sysvar">binlog_format</literal>.
+ For example, DDL statements such as
+ <literal role="stmt">CREATE TABLE</literal> and
+ <literal role="stmt">ALTER TABLE</literal> are always logged
+ as statements, without regard to the logging format in effect,
+ so the following statement-based rules for
+ <option>--binlog-ignore-db</option> always apply in
+ determining whether or not the statement is logged.
</para>
<formalpara>
Modified: trunk/refman-5.5/replication-options-core.xml
===================================================================
--- trunk/refman-5.5/replication-options-core.xml 2010-09-17 16:39:01 UTC (rev 22762)
+++ trunk/refman-5.5/replication-options-core.xml 2010-09-17 17:27:00 UTC (rev 22763)
Changed blocks: 2, Lines Added: 20, Lines Deleted: 0; 2046 bytes
@@ -2576,6 +2576,16 @@
same way that the effects of
<option role="mysqld">--replicate-do-db</option> depend on
whether statement-based or row-based replication is in use.
+ You should keep in mind that the format used to log a given
+ statement may not necessarily be the same as that indicated by
+ the value of <literal role="sysvar">binlog_format</literal>.
+ For example, DDL statements such as
+ <literal role="stmt">CREATE TABLE</literal> and
+ <literal role="stmt">ALTER TABLE</literal> are always logged
+ as statements, without regard to the logging format in effect,
+ so the following statement-based rules for
+ <option>--binlog-do-db</option> always apply in determining
+ whether or not the statement is logged.
</para>
<formalpara>
@@ -2740,6 +2750,16 @@
same way that the effects of
<option role="mysqld">--replicate-ignore-db</option> depend on
whether statement-based or row-based replication is in use.
+ You should keep in mind that the format used to log a given
+ statement may not necessarily be the same as that indicated by
+ the value of <literal role="sysvar">binlog_format</literal>.
+ For example, DDL statements such as
+ <literal role="stmt">CREATE TABLE</literal> and
+ <literal role="stmt">ALTER TABLE</literal> are always logged
+ as statements, without regard to the logging format in effect,
+ so the following statement-based rules for
+ <option>--binlog-ignore-db</option> always apply in
+ determining whether or not the statement is logged.
</para>
<formalpara>
Modified: trunk/refman-5.6/replication-options-core.xml
===================================================================
--- trunk/refman-5.6/replication-options-core.xml 2010-09-17 16:39:01 UTC (rev 22762)
+++ trunk/refman-5.6/replication-options-core.xml 2010-09-17 17:27:00 UTC (rev 22763)
Changed blocks: 2, Lines Added: 20, Lines Deleted: 0; 2046 bytes
@@ -2719,6 +2719,16 @@
same way that the effects of
<option role="mysqld">--replicate-do-db</option> depend on
whether statement-based or row-based replication is in use.
+ You should keep in mind that the format used to log a given
+ statement may not necessarily be the same as that indicated by
+ the value of <literal role="sysvar">binlog_format</literal>.
+ For example, DDL statements such as
+ <literal role="stmt">CREATE TABLE</literal> and
+ <literal role="stmt">ALTER TABLE</literal> are always logged
+ as statements, without regard to the logging format in effect,
+ so the following statement-based rules for
+ <option>--binlog-do-db</option> always apply in determining
+ whether or not the statement is logged.
</para>
<formalpara>
@@ -2883,6 +2893,16 @@
same way that the effects of
<option role="mysqld">--replicate-ignore-db</option> depend on
whether statement-based or row-based replication is in use.
+ You should keep in mind that the format used to log a given
+ statement may not necessarily be the same as that indicated by
+ the value of <literal role="sysvar">binlog_format</literal>.
+ For example, DDL statements such as
+ <literal role="stmt">CREATE TABLE</literal> and
+ <literal role="stmt">ALTER TABLE</literal> are always logged
+ as statements, without regard to the logging format in effect,
+ so the following statement-based rules for
+ <option>--binlog-ignore-db</option> always apply in
+ determining whether or not the statement is logged.
</para>
<formalpara>
Modified: trunk/refman-6.0/replication-options-core.xml
===================================================================
--- trunk/refman-6.0/replication-options-core.xml 2010-09-17 16:39:01 UTC (rev 22762)
+++ trunk/refman-6.0/replication-options-core.xml 2010-09-17 17:27:00 UTC (rev 22763)
Changed blocks: 2, Lines Added: 20, Lines Deleted: 0; 2046 bytes
@@ -2578,6 +2578,16 @@
same way that the effects of
<option role="mysqld">--replicate-do-db</option> depend on
whether statement-based or row-based replication is in use.
+ You should keep in mind that the format used to log a given
+ statement may not necessarily be the same as that indicated by
+ the value of <literal role="sysvar">binlog_format</literal>.
+ For example, DDL statements such as
+ <literal role="stmt">CREATE TABLE</literal> and
+ <literal role="stmt">ALTER TABLE</literal> are always logged
+ as statements, without regard to the logging format in effect,
+ so the following statement-based rules for
+ <option>--binlog-do-db</option> always apply in determining
+ whether or not the statement is logged.
</para>
<formalpara>
@@ -2742,6 +2752,16 @@
same way that the effects of
<option role="mysqld">--replicate-ignore-db</option> depend on
whether statement-based or row-based replication is in use.
+ You should keep in mind that the format used to log a given
+ statement may not necessarily be the same as that indicated by
+ the value of <literal role="sysvar">binlog_format</literal>.
+ For example, DDL statements such as
+ <literal role="stmt">CREATE TABLE</literal> and
+ <literal role="stmt">ALTER TABLE</literal> are always logged
+ as statements, without regard to the logging format in effect,
+ so the following statement-based rules for
+ <option>--binlog-ignore-db</option> always apply in
+ determining whether or not the statement is logged.
</para>
<formalpara>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r22763 - in trunk: refman-5.1 refman-5.5 refman-5.6 refman-6.0 | jon.stephens | 17 Sep |
