Author: jstephens
Date: 2007-07-05 15:50:19 +0200 (Thu, 05 Jul 2007)
New Revision: 7022
Log:
Documented misc. Server bugfixes:
Bug #10491
Bug #19443
Bug #23051
Bug #28722
Bug #28430
Modified:
trunk/refman-5.0/releasenotes-es-5.0.xml
trunk/refman-5.1/news-5.1.xml
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-07-05 12:54:03 UTC (rev 7021)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-07-05 13:50:19 UTC (rev 7022)
Changed blocks: 1, Lines Added: 9, Lines Deleted: 0; 835 bytes
@@ -94,6 +94,15 @@
<listitem>
<para>
+ The server returned data from <literal>SHOW CREATE
+ TABLE</literal> statement or a <literal>SELECT</literal>
+ statement on an INFORMATION_SCHEMA table using the
+ <literal>binary</literal> character set. (Bug #10491)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>NDB Cluster</literal>: The management client's
response to <literal>START BACKUP WAIT COMPLETED</literal> did
not include the backup ID. (Bug #27640)
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-07-05 12:54:03 UTC (rev 7021)
+++ trunk/refman-5.1/news-5.1.xml 2007-07-05 13:50:19 UTC (rev 7022)
Changed blocks: 1, Lines Added: 62, Lines Deleted: 0; 2700 bytes
@@ -80,6 +80,68 @@
<listitem>
<para>
+ Replication of partitioned tables using the
+ <literal>InnoDB</literal> storage engine failed with
+ <literal>binlog-format=ROW</literal> or
+ <literal>binlog-format=MIXED</literal>. (Bug #28430)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>SHOW TRIGGERS</literal> did not handle non-Latin
+ symbols in column names correctly;
+ <command>mysqldump</command> also did not work properly with
+ such triggers. Both of these issues were also related to
+ improper handling of non-Latin characters sets in
+ <literal>INFORMATION_SCHEMA</literal> tables. (Bug #19443)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ If a storage engine has its own logging capability, then any
+ statement using both this engine and some other engine not
+ having its own logging could not be correctly logged, due to
+ the fact that entries from one engine could be logged before
+ entries from the other engine were. This did not generate any
+ error messages when it occurred.
+ </para>
+
+ <para>
+ Now, if multiple storage engines are used in a statement and
+ at least one of them has its own logging capability, then an
+ error message is generated and the statement is not executed.
+ (Bug #28722)
+ </para>
+
+ <note>
+ <para>
+ Currently, the only storage engine to have its own logging
+ capability is <literal>NDBCLUSTER</literal>.
+ </para>
+ </note>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using the <literal>READ COMMITTED</literal> transaction
+ isolation level caused mixed and statement-based replication
+ to fail. (Bug #23051)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The server returned data from <literal>SHOW CREATE
+ TABLE</literal> statement or a <literal>SELECT</literal>
+ statement on an INFORMATION_SCHEMA table using the
+ <literal>binary</literal> character set. (Bug #10491)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>NDB Cluster</literal> (Cluster Replication): When
executing a statement where
<literal>binlog_format=statement</literal>, the result of the
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r7022 - in trunk: refman-5.0 refman-5.1 | jon | 5 Jul |
