Author: jstephens
Date: 2008-04-02 23:00:08 +0200 (Wed, 02 Apr 2008)
New Revision: 10408
Log:
Documenting bugfixes (mostly CGE-6.3.11):
Bug #34201, Bug #34208, Bug #34247, Bug #34305, Bug #34337,
Bug #34355, Bug #34358, Bug #34515, Bug #34507, Bug #34620,
Bug #34643, Bug #34655, Bug #34686, Bug #34732, Bug #34749,
Bug #34756, Bug #34757, Bug #34768, Bug #34788
Modified:
trunk/dynamic-docs/changelog/mysqld-1.xml
trunk/refman-5.1/replication-notes.xml
Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml 2008-04-02 19:12:13 UTC (rev 10407)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml 2008-04-02 21:00:08 UTC (rev 10408)
Changed blocks: 14, Lines Added: 191, Lines Deleted: 3; 6695 bytes
@@ -9,6 +9,179 @@
<logentry entrytype="bug">
<tags>
+ <manual type="FEDERATED"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="34788"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.60"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
+ <version ver="5.1.24"/>
+ <version ver="6.0.5"/>
+ </versions>
+
+ <message>
+
+ <para>
+ A malformed URL used for a <literal>FEDERATED</literal>
+ table's <literal>CONNECTION</literal> option value in a
+ <literal>CREATE TABLE</literal> statement was not handled
+ correctly and could crash the server.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="cluster"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="34756"/>
+ <regressionof bugid="34033"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.23-ndb-6.3.11"/>
+ </versions>
+
+ <message>
+
+ <para>
+ In some situations, a problem with synchronizing checkpoints
+ between nodes could cause a system restart or a node restart to
+ fail with <errortext>Error 630 during restore of TX</errortext>.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <manual type="TRUNCATE"/>
+ <manual type="triggers"/>
+ <manual type="foreign keys"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="34643"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.60"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
+ <version ver="5.1.24"/>
+ <version ver="6.0.5"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Executing a <literal>TRUNCATE</literal> statement on a table
+ having both a foreign key reference and a
+ <literal>DELETE</literal> trigger crashed the server.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="cluster"/>
+ <manual type="indexes"/>
+ <manual type="DECIMAL"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="34515"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.23-ndb-6.3.11"/>
+ </versions>
+
+ <message>
+
+ <para>
+ When a secondary index on a <literal>DECIMAL</literal> column
+ was used to retrieve data from an <literal>NDB</literal> table,
+ no results were returned even if the target table had a matched
+ value in the column that was defined with the secondary index.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="cluster"/>
+ <manual type="UPDATE"/>
+ <manual type="unique keys"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="34208"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.23-ndb-6.3.11"/>
+ </versions>
+
+ <message>
+
+ <para>
+ An <literal>UPDATE</literal> on an <literal>NDB</literal> table
+ that set a new value for a unique key column could cause
+ subsequent queries to fail.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="cluster"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="34201"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.23-ndb-6.3.11"/>
+ </versions>
+
+ <message>
+
+ <para>
+ If a data node in one node group was placed in the <quote>not
+ started</quote> state (using
+ <literal><replaceable>node_id</replaceable> RESTART
+ -n</literal>), it was not possible to stop a data node in a
+ different node group.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
<highlight type="importantchange"/>
<manual type="FRAC_SECOND"/>
<manual type="MICROSECOND"/>
@@ -754,6 +927,7 @@
</bugs>
<versions>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -790,6 +964,7 @@
<versions>
<version ver="5.0.60"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -1009,6 +1184,7 @@
</bugs>
<versions>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -1097,6 +1273,7 @@
</bugs>
<versions>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="6.0.5"/>
</versions>
@@ -1527,6 +1704,7 @@
<versions>
<version ver="5.0.60"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -1741,6 +1919,7 @@
</bugs>
<versions>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -1876,6 +2055,7 @@
<versions>
<version ver="5.0.58"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -2009,6 +2189,7 @@
<versions>
<version ver="5.0.60"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -2040,6 +2221,7 @@
<versions>
<version ver="5.0.60"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -2440,14 +2622,16 @@
<versions>
<version ver="5.1.23-ndb-6.2.14"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
</versions>
<message>
<para>
- The --ndb-wait-connected option caused the server to wait for a
- partial connection plus an additional 3 seconds for a complete
- connection to the cluster.
+ The <option>--ndb-wait-connected</option> option caused the
+ server to wait for a partial connection plus an additional 3
+ seconds for a complete connection to the cluster. This could
+ lead to issues with setting up the binary log.
</para>
</message>
@@ -2468,6 +2652,7 @@
<versions>
<version ver="5.1.23-ndb-6.2.14"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
</versions>
@@ -3042,6 +3227,7 @@
<versions>
<version ver="5.0.48"/>
<version ver="5.1.23-ndb-6.2.14"/>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
@@ -13615,7 +13801,9 @@
</bugs>
<versions>
+ <version ver="5.1.23-ndb-6.3.11"/>
<version ver="5.1.24"/>
+ <version ver="6.0.5"/>
</versions>
<message>
Modified: trunk/refman-5.1/replication-notes.xml
===================================================================
--- trunk/refman-5.1/replication-notes.xml 2008-04-02 19:12:13 UTC (rev 10407)
+++ trunk/refman-5.1/replication-notes.xml 2008-04-02 21:00:08 UTC (rev 10408)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 1; 696 bytes
@@ -957,7 +957,8 @@
in <literal>DELETE</literal>, <literal>UPDATE</literal>, and
<literal>INSERT ... SELECT</literal> statements is unsafe since
the order of the rows affected is not defined. Beginning with
- MySQL 5.1.24, when such a statement is encountered:
+ MySQL 5.1.24 (&mccge-series;: MySQL 5.1.23-ndb-6.3.11), when
+ such a statement is encountered:
<itemizedlist>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r10408 - in trunk: dynamic-docs/changelog refman-5.1 | jon | 2 Apr |
