List:Commits« Previous MessageNext Message »
From:jon.stephens Date:March 30 2010 12:55pm
Subject:svn commit - mysqldoc@docsrva: r19769 - in trunk: dynamic-docs/changelog refman-5.5 refman-6.0
View as plain text  
Author: jstephens
Date: 2010-03-30 14:55:18 +0200 (Tue, 30 Mar 2010)
New Revision: 19769

Log:

Fixes / Closes BUG#39934



Modified:
   trunk/dynamic-docs/changelog/mysqld-2.xml
   trunk/refman-5.5/dba-log-files.xml
   trunk/refman-6.0/dba-log-files.xml


Modified: trunk/dynamic-docs/changelog/mysqld-2.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-2.xml	2010-03-30 12:53:45 UTC (rev 19768)
+++ trunk/dynamic-docs/changelog/mysqld-2.xml	2010-03-30 12:55:18 UTC (rev 19769)
Changed blocks: 1, Lines Added: 6, Lines Deleted: 0; 750 bytes

@@ -3519,6 +3519,12 @@
       </para>
 
       <para>
+        For information about changes in how the binary logging format
+        is determined in relation to statement type and storage engine
+        logging capabilities, see <xref linkend="binary-log-mixed"/>.
+      </para>
+
+      <para>
         As part of the fix for this issue, the
         <literal role="se">EXAMPLE</literal> storage engine is now
         changed so that it supports statement-based logging only.


Modified: trunk/refman-5.5/dba-log-files.xml
===================================================================
--- trunk/refman-5.5/dba-log-files.xml	2010-03-30 12:53:45 UTC (rev 19768)
+++ trunk/refman-5.5/dba-log-files.xml	2010-03-30 12:55:18 UTC (rev 19769)
Changed blocks: 1, Lines Added: 304, Lines Deleted: 2; 13154 bytes

@@ -1776,8 +1776,310 @@
       </itemizedlist>
 
       <para>
-        When determining the logging mode to be used, the capabilities
-        of all the tables affected by the event are combined. The set of
+        In MySQL 5.5.3 and later, whether a statement is to be logged
+        and the logging mode to be used is determined according to the
+        type of statement (safe, unsafe, or binary injected), the binary
+        logging format (<literal>STATEMENT</literal>,
+        <literal>ROW</literal>, or <literal>MIXED</literal>), and the
+        logging capabailities of the storage engine (statement-capable,
+        row-capable, both, or neither). Statements may be logged with or
+        without a warning; failed statements are not logged, but
+        generate errors in the log. This is shown in the following
+        decision table:
+      </para>
+
+      <informaltable>
+        <tgroup cols="6">
+          <colspec colwidth="10*" colname="type"/>
+          <colspec colwidth="25*" colname="format"/>
+          <colspec colwidth="10*" colname="SLC"/>
+          <colspec colwidth="10*" colname="RLC"/>
+          <colspec colwidth="20*" colname="error"/>
+          <colspec colwidth="25*" colname="logas"/>
+          <spanspec namest="type" nameend="RLC" spanname="condition"/>
+          <spanspec namest="error" nameend="logas" spanname="action"/>
+          <thead>
+            <row>
+              <entry spanname="condition">Condition</entry>
+              <entry spanname="action">Action</entry>
+            </row>
+            <row>
+              <entry>Type</entry>
+              <entry><literal role="sysvar">binlog_format</literal></entry>
+              <entry>SLC</entry>
+              <entry>RLC</entry>
+              <entry>Error / Warning</entry>
+              <entry>Logged as</entry>
+            </row>
+          </thead>
+          <tbody>
+            <row>
+              <entry>*</entry>
+              <entry><literal>*</literal></entry>
+              <entry>No</entry>
+              <entry>No</entry>
+              <entry><errortext>Error: Cannot execute statement</errortext>: Binary logging
+                is impossible since at least one engine is involved that
+                is both row-incapable and statement-incapable.</entry>
+              <entry><literal>-</literal></entry>
+            </row>
+            <row>
+              <entry>Safe</entry>
+              <entry><literal>STATEMENT</literal></entry>
+              <entry>Yes</entry>
+              <entry>No</entry>
+              <entry>-</entry>
+              <entry><literal>STATEMENT</literal></entry>
+            </row>
+            <row>
+              <entry>Safe</entry>
+              <entry><literal>MIXED</literal></entry>
+              <entry>Yes</entry>
+              <entry>No</entry>
+              <entry>-</entry>
+              <entry><literal>STATEMENT</literal></entry>
+            </row>
+            <row>
+              <entry>Safe</entry>
+              <entry><literal>ROW</literal></entry>
+              <entry>Yes</entry>
+              <entry>No</entry>
+              <entry><errortext>Error: Cannot execute statement</errortext>: Binary logging
+                is impossible since <literal>BINLOG_FORMAT =
+                ROW</literal> and at least one table uses a storage
+                engine that is not capable of row-based logging.</entry>
+              <entry><literal>-</literal></entry>
+            </row>
+            <row>
+              <entry>Unsafe</entry>
+              <entry><literal>STATEMENT</literal></entry>
+              <entry>Yes</entry>
+              <entry>No</entry>
+              <entry><errortext>Warning: Unsafe statement binlogged in statement
+                format</errortext>, since <literal>BINLOG_FORMAT =
+                STATEMENT</literal></entry>
+              <entry><literal>STATEMENT</literal>.</entry>
+              <entry><literal>STATEMENT</literal></entry>
+            </row>
+            <row>
+              <entry>Unsafe</entry>
+              <entry><literal>MIXED</literal></entry>
+              <entry>Yes</entry>
+              <entry>No</entry>
+              <entry><errortext>Error: Cannot execute statement</errortext>: Binary logging
+                of an unsafe statement is impossible when the storage
+                engine is limited to statement-based logging, even if
+                <literal>BINLOG_FORMAT = MIXED</literal>.</entry>
+              <entry><literal>-</literal></entry>
+            </row>
+            <row>
+              <entry>Unsafe</entry>
+              <entry><literal>ROW</literal></entry>
+              <entry>Yes</entry>
+              <entry>No</entry>
+              <entry><errortext>Error: Cannot execute statement</errortext>: Binary logging
+                is impossible since <literal>BINLOG_FORMAT =
+                ROW</literal> and at least one table uses a storage
+                engine that is not capable of row-based logging.</entry>
+              <entry>-</entry>
+            </row>
+            <row>
+              <entry>Row Injection</entry>
+              <entry><literal>STATEMENT</literal></entry>
+              <entry>Yes</entry>
+              <entry>No</entry>
+              <entry><errortext>Error: Cannot execute row injection</errortext>: Binary
+                logging is not possible since at least one table uses a
+                storage engine that is not capable of row-based logging.</entry>
+              <entry>-</entry>
+            </row>
+            <row>
+              <entry>Row Injection</entry>
+              <entry><literal>MIXED</literal></entry>
+              <entry>Yes</entry>
+              <entry>No</entry>
+              <entry><errortext>Error: Cannot execute row injection</errortext>: Binary
+                logging is not possible since at least one table uses a
+                storage engine that is not capable of row-based logging.</entry>
+              <entry>-</entry>
+            </row>
+            <row>
+              <entry>Row Injection</entry>
+              <entry><literal>ROW</literal></entry>
+              <entry>Yes</entry>
+              <entry>No</entry>
+              <entry><errortext>Error: Cannot execute row injection</errortext>: Binary
+                logging is not possible since at least one table uses a
+                storage engine that is not capable of row-based logging.</entry>
+              <entry>-</entry>
+            </row>
+            <row>
+              <entry>Safe</entry>
+              <entry><literal>STATEMENT</literal></entry>
+              <entry>No</entry>
+              <entry>Yes</entry>
+              <entry><errortext>Error: Cannot execute statement</errortext>: Binary logging
+                is impossible since <literal>BINLOG_FORMAT =
+                STATEMENT</literal> and at least one table uses a
+                storage engine that is not capable of statement-based
+                logging.</entry>
+              <entry><literal>-</literal></entry>
+            </row>
+            <row>
+              <entry>Safe</entry>
+              <entry><literal>MIXED</literal></entry>
+              <entry>No</entry>
+              <entry>Yes</entry>
+              <entry>-</entry>
+              <entry><literal>ROW</literal></entry>
+            </row>
+            <row>
+              <entry>Safe</entry>
+              <entry><literal>ROW</literal></entry>
+              <entry>No</entry>
+              <entry>Yes</entry>
+              <entry>-</entry>
+              <entry><literal>ROW</literal></entry>
+            </row>
+            <row>
+              <entry>Unsafe</entry>
+              <entry><literal>STATEMENT</literal></entry>
+              <entry>No</entry>
+              <entry>Yes</entry>
+              <entry><errortext>Error: Cannot execute statement</errortext>: Binary logging
+                is impossible since <literal>BINLOG_FORMAT =
+                STATEMENT</literal> and at least one table uses a
+                storage engine that is not capable of statement-based
+                logging.</entry>
+              <entry>-</entry>
+            </row>
+            <row>
+              <entry>Unsafe</entry>
+              <entry><literal>MIXED</literal></entry>
+              <entry>No</entry>
+              <entry>Yes</entry>
+              <entry>-</entry>
+              <entry><literal>ROW</literal></entry>
+            </row>
+            <row>
+              <entry>Unsafe</entry>
+              <entry><literal>ROW</literal></entry>
+              <entry>No</entry>
+              <entry>Yes</entry>
+              <entry>-</entry>
+              <entry><literal>ROW</literal></entry>
+            </row>
+            <row>
+              <entry>Row Injection</entry>
+              <entry><literal>STATEMENT</literal></entry>
+              <entry>No</entry>
+              <entry>Yes</entry>
+              <entry><errortext>Error: Cannot execute row injection</errortext>: Binary
+                logging is not possible since <literal>BINLOG_FORMAT =
+                STATEMENT</literal>.</entry>
+              <entry><literal>-</literal></entry>
+            </row>
+            <row>
+              <entry>Row Injection</entry>
+              <entry><literal>MIXED</literal></entry>
+              <entry>No</entry>
+              <entry>Yes</entry>
+              <entry>-</entry>
+              <entry><literal>ROW</literal></entry>
+            </row>
+            <row>
+              <entry>Row Injection</entry>
+              <entry><literal>ROW</literal></entry>
+              <entry>No</entry>
+              <entry>Yes</entry>
+              <entry>-</entry>
+              <entry><literal>ROW</literal></entry>
+            </row>
+            <row>
+              <entry>Safe</entry>
+              <entry><literal>STATEMENT</literal></entry>
+              <entry>Yes</entry>
+              <entry>Yes</entry>
+              <entry>-</entry>
+              <entry><literal>STATEMENT</literal></entry>
+            </row>
+            <row>
+              <entry>Safe</entry>
+              <entry><literal>MIXED</literal></entry>
+              <entry>Yes</entry>
+              <entry>Yes</entry>
+              <entry>-</entry>
+              <entry><literal>ROW</literal></entry>
+            </row>
+            <row>
+              <entry>Safe</entry>
+              <entry><literal>ROW</literal></entry>
+              <entry>Yes</entry>
+              <entry>Yes</entry>
+              <entry>-</entry>
+              <entry><literal>ROW</literal></entry>
+            </row>
+            <row>
+              <entry>Unsafe</entry>
+              <entry><literal>STATEMENT</literal></entry>
+              <entry>Yes</entry>
+              <entry>Yes</entry>
+              <entry><errortext>Warning: Unsafe statement binlogged in statement
+                format</errortext> since <literal>BINLOG_FORMAT =
+                STATEMENT</literal>.</entry>
+              <entry><literal>STATEMENT</literal></entry>
+            </row>
+            <row>
+              <entry>Unsafe</entry>
+              <entry><literal>MIXED</literal></entry>
+              <entry>Yes</entry>
+              <entry>Yes</entry>
+              <entry>-</entry>
+              <entry><literal>ROW</literal></entry>
+            </row>
+            <row>
+              <entry>Unsafe</entry>
+              <entry><literal>ROW</literal></entry>
+              <entry>Yes</entry>
+              <entry>Yes</entry>
+              <entry>-</entry>
+              <entry><literal>ROW</literal></entry>
+            </row>
+            <row>
+              <entry>Row Injection</entry>
+              <entry><literal>STATEMENT</literal></entry>
+              <entry>Yes</entry>
+              <entry>Yes</entry>
+              <entry><errortext>Error: Cannot execute row injection</errortext>: Binary
+                logging is not possible because <literal>BINLOG_FORMAT =
+                STATEMENT</literal>.</entry>
+              <entry>-</entry>
+            </row>
+            <row>
+              <entry>Row Injection</entry>
+              <entry><literal>MIXED</literal></entry>
+              <entry>Yes</entry>
+              <entry>Yes</entry>
+              <entry>-</entry>
+              <entry><literal>ROW</literal></entry>
+            </row>
+            <row>
+              <entry>Row Injection</entry>
+              <entry><literal>ROW</literal></entry>
+              <entry>Yes</entry>
+              <entry>Yes</entry>
+              <entry>-</entry>
+              <entry><literal>ROW</literal></entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </informaltable>
+
+      <para>
+        The decision-making process for bainary logging changed in MySQL
+        5.5.3, due to the fix for Bug#39934. Prior to MySQL 5.5.3, when
+        determining the logging mode to be used, the capabilities of all
+        the tables affected by the event are combined, and the set of
         affected tables is then marked according to these rules:
       </para>
 


Modified: trunk/refman-6.0/dba-log-files.xml
===================================================================
--- trunk/refman-6.0/dba-log-files.xml	2010-03-30 12:53:45 UTC (rev 19768)
+++ trunk/refman-6.0/dba-log-files.xml	2010-03-30 12:55:18 UTC (rev 19769)
Changed blocks: 1, Lines Added: 305, Lines Deleted: 3; 13262 bytes

@@ -1830,11 +1830,313 @@
       </itemizedlist>
 
       <para>
-        When determining the logging mode to be used, the capabilities
-        of all the tables affected by the event are combined. The set of
-        affected tables is then marked according to these rules:
+        In MySQL 6.0.14 and later, whether a statement is to be logged
+        and the logging mode to be used is determined according to the
+        type of statement (safe, unsafe, or binary injected), the binary
+        logging format (<literal>STATEMENT</literal>,
+      <literal>ROW</literal>, or <literal>MIXED</literal>), and the
+        logging capabailities of the storage engine (statement-capable,
+        row-capable, both, or neither). Statements may be logged with or
+        without a warning; failed statements are not logged, but
+        generate errors in the log. This is shown in the following
+        decision table:
       </para>
 
+      <informaltable>
+        <tgroup cols="6">
+          <colspec colwidth="10*" colname="type"/>
+          <colspec colwidth="25*" colname="format"/>
+          <colspec colwidth="10*" colname="SLC"/>
+          <colspec colwidth="10*" colname="RLC"/>
+          <colspec colwidth="20*" colname="error"/>
+          <colspec colwidth="25*" colname="logas"/>
+          <spanspec namest="type" nameend="RLC" spanname="condition"/>
+          <spanspec namest="error" nameend="logas" spanname="action"/>
+          <thead>
+            <row>
+              <entry spanname="condition">Condition</entry>
+              <entry spanname="action">Action</entry>
+            </row>
+            <row>
+              <entry>Type</entry>
+              <entry><literal role="sysvar">binlog_format</literal></entry>
+              <entry>SLC</entry>
+              <entry>RLC</entry>
+              <entry>Error / Warning</entry>
+              <entry>Logged as</entry>
+            </row>
+          </thead>
+          <tbody>
+            <row>
+              <entry>*</entry>
+              <entry><literal>*</literal></entry>
+              <entry>No</entry>
+              <entry>No</entry>
+              <entry><errortext>Error: Cannot execute statement</errortext>: Binary logging
+                is impossible since at least one engine is involved that
+                is both row-incapable and statement-incapable.</entry>
+              <entry><literal>-</literal></entry>
+            </row>
+            <row>
+              <entry>Safe</entry>
+              <entry><literal>STATEMENT</literal></entry>
+              <entry>Yes</entry>
+              <entry>No</entry>
+              <entry>-</entry>
+              <entry><literal>STATEMENT</literal></entry>
+            </row>
+            <row>
+              <entry>Safe</entry>
+              <entry><literal>MIXED</literal></entry>
+              <entry>Yes</entry>
+              <entry>No</entry>
+              <entry>-</entry>
+              <entry><literal>STATEMENT</literal></entry>
+            </row>
+            <row>
+              <entry>Safe</entry>
+              <entry><literal>ROW</literal></entry>
+              <entry>Yes</entry>
+              <entry>No</entry>
+              <entry><errortext>Error: Cannot execute statement</errortext>: Binary logging
+                is impossible since <literal>BINLOG_FORMAT =
+                ROW</literal> and at least one table uses a storage
+                engine that is not capable of row-based logging.</entry>
+              <entry><literal>-</literal></entry>
+            </row>
+            <row>
+              <entry>Unsafe</entry>
+              <entry><literal>STATEMENT</literal></entry>
+              <entry>Yes</entry>
+              <entry>No</entry>
+              <entry><errortext>Warning: Unsafe statement binlogged in statement
+                format</errortext>, since <literal>BINLOG_FORMAT =
+                STATEMENT</literal></entry>
+              <entry><literal>STATEMENT</literal>.</entry>
+              <entry><literal>STATEMENT</literal></entry>
+            </row>
+            <row>
+              <entry>Unsafe</entry>
+              <entry><literal>MIXED</literal></entry>
+              <entry>Yes</entry>
+              <entry>No</entry>
+              <entry><errortext>Error: Cannot execute statement</errortext>: Binary logging
+                of an unsafe statement is impossible when the storage
+                engine is limited to statement-based logging, even if
+                <literal>BINLOG_FORMAT = MIXED</literal>.</entry>
+              <entry><literal>-</literal></entry>
+            </row>
+            <row>
+              <entry>Unsafe</entry>
+              <entry><literal>ROW</literal></entry>
+              <entry>Yes</entry>
+              <entry>No</entry>
+              <entry><errortext>Error: Cannot execute statement</errortext>: Binary logging
+                is impossible since <literal>BINLOG_FORMAT =
+                ROW</literal> and at least one table uses a storage
+                engine that is not capable of row-based logging.</entry>
+              <entry>-</entry>
+            </row>
+            <row>
+              <entry>Row Injection</entry>
+              <entry><literal>STATEMENT</literal></entry>
+              <entry>Yes</entry>
+              <entry>No</entry>
+              <entry><errortext>Error: Cannot execute row injection</errortext>: Binary
+                logging is not possible since at least one table uses a
+                storage engine that is not capable of row-based logging.</entry>
+              <entry>-</entry>
+            </row>
+            <row>
+              <entry>Row Injection</entry>
+              <entry><literal>MIXED</literal></entry>
+              <entry>Yes</entry>
+              <entry>No</entry>
+              <entry><errortext>Error: Cannot execute row injection</errortext>: Binary
+                logging is not possible since at least one table uses a
+                storage engine that is not capable of row-based logging.</entry>
+              <entry>-</entry>
+            </row>
+            <row>
+              <entry>Row Injection</entry>
+              <entry><literal>ROW</literal></entry>
+              <entry>Yes</entry>
+              <entry>No</entry>
+              <entry><errortext>Error: Cannot execute row injection</errortext>: Binary
+                logging is not possible since at least one table uses a
+                storage engine that is not capable of row-based logging.</entry>
+              <entry>-</entry>
+            </row>
+            <row>
+              <entry>Safe</entry>
+              <entry><literal>STATEMENT</literal></entry>
+              <entry>No</entry>
+              <entry>Yes</entry>
+              <entry><errortext>Error: Cannot execute statement</errortext>: Binary logging
+                is impossible since <literal>BINLOG_FORMAT =
+                STATEMENT</literal> and at least one table uses a
+                storage engine that is not capable of statement-based
+                logging.</entry>
+              <entry><literal>-</literal></entry>
+            </row>
+            <row>
+              <entry>Safe</entry>
+              <entry><literal>MIXED</literal></entry>
+              <entry>No</entry>
+              <entry>Yes</entry>
+              <entry>-</entry>
+              <entry><literal>ROW</literal></entry>
+            </row>
+            <row>
+              <entry>Safe</entry>
+              <entry><literal>ROW</literal></entry>
+              <entry>No</entry>
+              <entry>Yes</entry>
+              <entry>-</entry>
+              <entry><literal>ROW</literal></entry>
+            </row>
+            <row>
+              <entry>Unsafe</entry>
+              <entry><literal>STATEMENT</literal></entry>
+              <entry>No</entry>
+              <entry>Yes</entry>
+              <entry><errortext>Error: Cannot execute statement</errortext>: Binary logging
+                is impossible since <literal>BINLOG_FORMAT =
+                STATEMENT</literal> and at least one table uses a
+                storage engine that is not capable of statement-based
+                logging.</entry>
+              <entry>-</entry>
+            </row>
+            <row>
+              <entry>Unsafe</entry>
+              <entry><literal>MIXED</literal></entry>
+              <entry>No</entry>
+              <entry>Yes</entry>
+              <entry>-</entry>
+              <entry><literal>ROW</literal></entry>
+            </row>
+            <row>
+              <entry>Unsafe</entry>
+              <entry><literal>ROW</literal></entry>
+              <entry>No</entry>
+              <entry>Yes</entry>
+              <entry>-</entry>
+              <entry><literal>ROW</literal></entry>
+            </row>
+            <row>
+              <entry>Row Injection</entry>
+              <entry><literal>STATEMENT</literal></entry>
+              <entry>No</entry>
+              <entry>Yes</entry>
+              <entry><errortext>Error: Cannot execute row injection</errortext>: Binary
+                logging is not possible since <literal>BINLOG_FORMAT =
+                STATEMENT</literal>.</entry>
+              <entry><literal>-</literal></entry>
+            </row>
+            <row>
+              <entry>Row Injection</entry>
+              <entry><literal>MIXED</literal></entry>
+              <entry>No</entry>
+              <entry>Yes</entry>
+              <entry>-</entry>
+              <entry><literal>ROW</literal></entry>
+            </row>
+            <row>
+              <entry>Row Injection</entry>
+              <entry><literal>ROW</literal></entry>
+              <entry>No</entry>
+              <entry>Yes</entry>
+              <entry>-</entry>
+              <entry><literal>ROW</literal></entry>
+            </row>
+            <row>
+              <entry>Safe</entry>
+              <entry><literal>STATEMENT</literal></entry>
+              <entry>Yes</entry>
+              <entry>Yes</entry>
+              <entry>-</entry>
+              <entry><literal>STATEMENT</literal></entry>
+            </row>
+            <row>
+              <entry>Safe</entry>
+              <entry><literal>MIXED</literal></entry>
+              <entry>Yes</entry>
+              <entry>Yes</entry>
+              <entry>-</entry>
+              <entry><literal>ROW</literal></entry>
+            </row>
+            <row>
+              <entry>Safe</entry>
+              <entry><literal>ROW</literal></entry>
+              <entry>Yes</entry>
+              <entry>Yes</entry>
+              <entry>-</entry>
+              <entry><literal>ROW</literal></entry>
+            </row>
+            <row>
+              <entry>Unsafe</entry>
+              <entry><literal>STATEMENT</literal></entry>
+              <entry>Yes</entry>
+              <entry>Yes</entry>
+              <entry><errortext>Warning: Unsafe statement binlogged in statement
+                format</errortext> since <literal>BINLOG_FORMAT =
+                STATEMENT</literal>.</entry>
+              <entry><literal>STATEMENT</literal></entry>
+            </row>
+            <row>
+              <entry>Unsafe</entry>
+              <entry><literal>MIXED</literal></entry>
+              <entry>Yes</entry>
+              <entry>Yes</entry>
+              <entry>-</entry>
+              <entry><literal>ROW</literal></entry>
+            </row>
+            <row>
+              <entry>Unsafe</entry>
+              <entry><literal>ROW</literal></entry>
+              <entry>Yes</entry>
+              <entry>Yes</entry>
+              <entry>-</entry>
+              <entry><literal>ROW</literal></entry>
+            </row>
+            <row>
+              <entry>Row Injection</entry>
+              <entry><literal>STATEMENT</literal></entry>
+              <entry>Yes</entry>
+              <entry>Yes</entry>
+              <entry><errortext>Error: Cannot execute row injection</errortext>: Binary
+                logging is not possible because <literal>BINLOG_FORMAT =
+                STATEMENT</literal>.</entry>
+              <entry>-</entry>
+            </row>
+            <row>
+              <entry>Row Injection</entry>
+              <entry><literal>MIXED</literal></entry>
+              <entry>Yes</entry>
+              <entry>Yes</entry>
+              <entry>-</entry>
+              <entry><literal>ROW</literal></entry>
+            </row>
+            <row>
+              <entry>Row Injection</entry>
+              <entry><literal>ROW</literal></entry>
+              <entry>Yes</entry>
+              <entry>Yes</entry>
+              <entry>-</entry>
+              <entry><literal>ROW</literal></entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </informaltable>
+
+      <para>
+        The decision-making process for bainary logging changed in MySQL
+        6.0.14, due to the fix for Bug#39934. Prior to MySQL 6.0.14,
+        when determining the logging mode to be used, the capabilities
+        of all the tables affected by the event are combined, and the
+        set of affected tables is then marked according to these rules:
+      </para>
+
       <itemizedlist>
 
         <listitem>


Thread
svn commit - mysqldoc@docsrva: r19769 - in trunk: dynamic-docs/changelog refman-5.5 refman-6.0jon.stephens30 Mar