Author: jstephens
Date: 2007-04-27 14:29:31 +0200 (Fri, 27 Apr 2007)
New Revision: 6245
Log:
Documenting fixes for Cluster Disk Data bugs:
Bug #24667, Bug #25296, Bug #27712
Modified:
trunk/refman-5.1/news-5.1.xml
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-04-27 09:59:52 UTC (rev 6244)
+++ trunk/refman-5.1/news-5.1.xml 2007-04-27 12:29:31 UTC (rev 6245)
Changed blocks: 2, Lines Added: 23, Lines Deleted: 16; 1952 bytes
@@ -205,6 +205,29 @@
The patches for Bug #19370 and Bug #21789 were reverted.
</para>
</listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Disk Data): When in single
+ user mode, it was possible to create log file groups and
+ tablespaces from any SQL node connected to the cluster. (Bug
+ #27712)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Disk Data): Changing a column
+ specification or issuing a <literal>TRUNCATE</literal>
+ statement on a Disk Data table caused the table to become an
+ in-memory table. (Bug #24667, Bug #25296)
+ </para>
+
+ <para>
+ This fix supersedes an incomplete fix that was made for this
+ issue in MySQL 5.1.15.
+ </para>
+ </listitem>
<listitem>
<para>
@@ -4752,22 +4775,6 @@
<listitem>
<para>
- <literal>NDB Cluster</literal> (Disk Data): Issuing a
- <literal>TRUNCATE</literal> statement on a Disk Data table
- caused the table to become an in-memory table. (Bug #25296)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <literal>NDB Cluster</literal> (Disk Data): Changing a column
- specification on a Disk Data table caused the table to become
- an in-memory table. (Bug #24667)
- </para>
- </listitem>
-
- <listitem>
- <para>
<literal>NDB Cluster</literal>: It was not possible to create
an <literal>NDB</literal> table with a key on two
<literal>VARCHAR</literal> columns where both columns had a
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r6245 - trunk/refman-5.1 | jon | 27 Apr |
