Author: mcbrown
Date: 2006-07-11 10:33:21 +0200 (Tue, 11 Jul 2006)
New Revision: 2696
Log:
Documenting Dev bugs #16218, #16611, #17294, #17877
Modified:
trunk/refman-common/news-4.1.xml
trunk/refman-common/news-5.0.xml
trunk/refman-common/news-5.1.xml
Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml 2006-07-11 08:04:51 UTC (rev 2695)
+++ trunk/refman-common/news-4.1.xml 2006-07-11 08:33:21 UTC (rev 2696)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 0; 748 bytes
@@ -223,6 +223,14 @@
<listitem>
<para>
+ Checking a spatial table (using <literal>CHECK
+ TABLE</literal>) with an index and only one row would indicate
+ a table corruption. (Bug #17877)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
For <literal>SELECT ... FOR UPDATE</literal> statements that
used <literal>DISTINCT</literal> or <literal>GROUP
BY</literal> over all key parts of a unique index (or primary
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2006-07-11 08:04:51 UTC (rev 2695)
+++ trunk/refman-common/news-5.0.xml 2006-07-11 08:33:21 UTC (rev 2696)
Changed blocks: 3, Lines Added: 20, Lines Deleted: 2; 1611 bytes
@@ -208,7 +208,7 @@
</para>
<itemizedlist>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Running
@@ -216,7 +216,7 @@
<option>--nowait-nodes=<replaceable>id</replaceable></option>
where <replaceable>id</replaceable> was the node ID of a node
that was already running would fail with an invalid error
- message. (Bug #20419)
+ message. (Bug #20419)
</para>
</listitem>
@@ -304,6 +304,24 @@
<listitem>
<para>
+ Using tables from MySQL 4.x in MySQL 5.x, in particular those
+ with <literal>VARCHAR</literal> fields and using
+ <literal>INSERT DELAYED</literal> to update data in the table
+ would result in either data corruption or a server crash. (Bug
+ #16611, Bug #16218, Bug #17294)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Checking a spatial table (using <literal>CHECK
+ TABLE</literal>) with an index and only one row would indicate
+ a table corruption. (Bug #17877)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>SHOW GRANTS FOR CURRENT_USER</literal> did not return
definer grants when executed in <literal>DEFINER</literal>
context (such as within a stored prodedure defined with
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-07-11 08:04:51 UTC (rev 2695)
+++ trunk/refman-common/news-5.1.xml 2006-07-11 08:33:21 UTC (rev 2696)
Changed blocks: 6, Lines Added: 25, Lines Deleted: 7; 2504 bytes
@@ -314,6 +314,24 @@
<listitem>
<para>
+ Using tables from MySQL 4.x in MySQL 5.x, in particular those
+ with <literal>VARCHAR</literal> fields and using
+ <literal>INSERT DELAYED</literal> to update data in the table
+ would result in either data corruption or a server crash. (Bug
+ #16611, Bug #16218, Bug #17294)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Checking a spatial table (using <literal>CHECK
+ TABLE</literal>) with an index and only one row would indicate
+ a table corruption. (Bug #17877)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
A <quote>table not found</quote> error could occur for
statements that called a function defined in another database.
(Bug #17199)
@@ -478,7 +496,7 @@
could cause errors or crash the server. (Bug #20583)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: A race condition could in some
@@ -486,7 +504,7 @@
#20897)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Running
@@ -494,10 +512,10 @@
<option>--nowait-nodes=<replaceable>id</replaceable></option>
where <replaceable>id</replaceable> was the node ID of a node
that was already running would fail with an invalid error
- message. (Bug #20419)
+ message. (Bug #20419)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: When stopping and restarting
@@ -505,7 +523,7 @@
sometimes hang in Phase 100. (Bug #19645)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: The
@@ -513,9 +531,9 @@
<literal>AVG_ROW_LENGTH</literal> columns of the
<literal>INFORMATION_SCHEMA.TABLES</literal> table did not
report the size of variable-width column values correctly.
- (Bug #18413)
+ (Bug #18413)
</para>
-
+
<para>
See <xref linkend="tables-table"/>, for more information.
</para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r2696 - trunk/refman-common | mcbrown | 11 Jul |
