Author: jstephens
Date: 2006-06-01 14:50:00 +0200 (Thu, 01 Jun 2006)
New Revision: 2246
Log:
Documenting Cluster bugfixes:
Bug #18483, Bug #18947, Bug #20142
Modified:
trunk/refman-common/news-5.1.xml
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-06-01 08:59:30 UTC (rev 2245)
+++ trunk/refman-common/news-5.1.xml 2006-06-01 12:50:00 UTC (rev 2246)
@@ -96,6 +96,40 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: <literal>SHOW ENGINE NDB
+ STATUS</literal> could sometimes return an incorrect value
+ of <literal>0</literal> for the latest epoch, which could
+ cause problems with synchronising the binlog. (Bug #20142)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: A <literal>CREATE
+ TABLE</literal> statement involving foreign key constraints
+ raised an error rather than being silently ignored (see
+ <xref linkend="create-table"/>). (Bug #18483)
+ </para>
+
+ <para>
+ This bug affected Cluster in MySQL 5.1 only.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Replication): Data definition
+ and data manipulation statements on different tables were not
+ serialised correctly in the binlog. For example, there was no
+ guarantee that a <literal>CREATE TABLE</literal> statement and
+ an update on a different table would occur in the same order
+ in the binlog as they did on the cluster being replicated.
+ (Bug #18947)
+ </para>
+ </listitem>
<listitem>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r2246 - trunk/refman-common | jon | 1 Jun |
