Author: jstephens
Date: 2006-03-31 10:01:57 +0200 (Fri, 31 Mar 2006)
New Revision: 1712
Log:
Documenting fixes for P1/showstopper bugs:
Bug #16583, Bug #15921, Bug #16474,
Bug #17705, Bug #17764, Bug #18153,
Bug #18306, Bug #18386, Bug #18464
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-03-30 20:48:11 UTC (rev 1711)
+++ trunk/refman-common/news-4.1.xml 2006-03-31 08:01:57 UTC (rev 1712)
@@ -193,6 +193,16 @@
<listitem>
<para>
+ <literal>MyISAM</literal>: Keys for which the first part of
+ the key was a <literal>CHAR</literal> or
+ <literal>VARCHAR</literal> column using the UTF-8 character
+ set and longer than 254 bytes could become corrupted. (Bug
+ #17705)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>NDB Cluster</literal>: A timeout in the handling of
an <literal>ABORT</literal> condition with more that 32
operations could yield a node failure. (Bug #18414)
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2006-03-30 20:48:11 UTC (rev 1711)
+++ trunk/refman-common/news-5.0.xml 2006-03-31 08:01:57 UTC (rev 1712)
@@ -236,6 +236,84 @@
<listitem>
<para>
+ A <literal>SELECT ... ORDER BY ...</literal> from a view
+ defined using a function could crash the server. An example of
+ such a view might be <literal>CREATE VIEW AS SELECT SQRT(c1)
+ FROM t1</literal>. (Bug #18386)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A <literal>DELETE</literal> using a subquery could crash the
+ server. (Bug #18306)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>REPAIR TABLE</literal>, <literal>OPTIMIZE
+ TABLE</literal>, and <literal>ALTER TABLE</literal>
+ operations on transactional tables could corrupt triggers
+ referencing those tables. (Bug #18153)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>MyISAM</literal>: Performing a bulk insert on a table
+ referenced by a trigger would crash the table. (Bug #17764)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>MyISAM</literal>: Keys for which the first part of
+ the key was a <literal>CHAR</literal> or
+ <literal>VARCHAR</literal> column using the UTF-8 character
+ set and longer than 254 bytes could become corrupted. (Bug
+ #17705)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using <literal>ORDER BY
+ <replaceable>intvar</replaceable></literal> within a stored
+ procedure (where <replaceable>intvar</replaceable> is an
+ integer variable or expression) would crash the server. (Bug
+ #16474)
+ </para>
+
+ <para>
+ <emphasis role="bold">Note</emphasis>: The use of an integer
+ <replaceable>i</replaceable> in an <literal>ORDER BY
+ <replaceable>i</replaceable></literal> clause for sorting
+ the result by the
+ <replaceable>i</replaceable><superscript>th</superscript>
+ column is deprecated (and non-standard). It should
+ <emphasis>not</emphasis> be used in new applications. See
+ <xref linkend="select"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Triggers created in MySQL 5.0.16 and earlier could not be
+ dropped after upgrading the server to 5.0.17 or later. (Bug
+ #15921)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A <literal>SELECT</literal> using a function against a nested
+ view would crash the server. (Bug #15683)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>NDB Cluster</literal>: Certain queries using
<literal>ORDER BY ... ASC</literal> in the
<literal>WHERE</literal> clause could return incorrect
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-03-30 20:48:11 UTC (rev 1711)
+++ trunk/refman-common/news-5.1.xml 2006-03-31 08:01:57 UTC (rev 1712)
@@ -169,9 +169,24 @@
<itemizedlist>
+ <listitem>
+ <para>
+ Building the server using
+ <option>--with-example-storage-engine</option> failed to
+ enable the <literal>EXAMPLE</literal> storage engine in the
+ server. (Bug #18464)
+ </para>
+ </listitem>
<listitem>
<para>
+ Triggers created in one version of the server could not be
+ dropped after upgrading to a newer version. (Bug #15921)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Queries using <literal>WHERE ... IS NULL</literal> returned
incorrect results from partitioned tables. (Bug #18070)
</para>
@@ -607,6 +622,59 @@
<listitem>
<para>
+ A <literal>SELECT ... ORDER BY ...</literal> from a view
+ defined using a function could crash the server. An example of
+ such a view might be <literal>CREATE VIEW AS SELECT SQRT(c1)
+ FROM t1</literal>. (Bug #18386)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>REPAIR TABLE</literal>, <literal>OPTIMIZE
+ TABLE</literal>, and <literal>ALTER TABLE</literal>
+ operations on transactional tables could corrupt triggers
+ referencing those tables. (Bug #18153)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>MyISAM</literal>: Performing a bulk insert on a table
+ referenced by a trigger would crash the table. (Bug #17764)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using <literal>ORDER BY
+ <replaceable>intvar</replaceable></literal> within a stored
+ procedure (where <replaceable>intvar</replaceable> is an
+ integer variable or expression) would crash the server. (Bug
+ #16474)
+ </para>
+
+ <para>
+ <emphasis role="bold">Note</emphasis>: The use of an integer
+ <replaceable>i</replaceable> in an <literal>ORDER BY
+ <replaceable>i</replaceable></literal> clause for sorting
+ the result by the
+ <replaceable>i</replaceable><superscript>th</superscript>
+ column is deprecated (and non-standard). It should
+ <emphasis>not</emphasis> be used in new applications. See
+ <xref linkend="select"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A <literal>SELECT</literal> using a function against a nested
+ view would crash the server. (Bug #15683)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>ALTER TABLE ... ADD COLUMN ... AFTER ...</literal>
failed when used on partitioned tables. (Bug #16806)
</para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1712 - trunk/refman-common | jon | 31 Mar |
