svn commit - mysqldoc@docsrva: r4879 - in trunk: . refman-4.1 refman-5.0 refman-5.1

[paul]

Author: paul
Date: 2007-02-09 21:37:09 +0100 (Fri, 09 Feb 2007)
New Revision: 4879

Log:
 r16061@frost:  paul | 2007-02-09 14:36:19 -0600
 Document bugfixes:
 Bug#20604
 Bug#23409
 Bug#24653
 Bug#24987
 Bug#25575


Modified:
   trunk/refman-4.1/news-4.1.xml
   trunk/refman-5.0/releasenotes-es-5.0.xml
   trunk/refman-5.1/news-5.1.xml

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:19608
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:16059
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:13520
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:19608
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:16061
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:13520


Modified: trunk/refman-4.1/news-4.1.xml
===================================================================
--- trunk/refman-4.1/news-4.1.xml	2007-02-09 18:57:39 UTC (rev 4878)
+++ trunk/refman-4.1/news-4.1.xml	2007-02-09 20:37:09 UTC (rev 4879)
Changed blocks: 2, Lines Added: 30, Lines Deleted: 0; 1806 bytes

@@ -226,6 +226,23 @@
 
       <listitem>
         <para>
+          The arguments of the <literal>ENCODE()</literal> and the
+          <literal>DECODE()</literal> functions were not printed
+          correctly, causing problems in the output of <literal>EXPLAIN
+          EXTENDED</literal>. (Bug #23409)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          A return value of <literal>-1</literal> from user-defined
+          handlers was not handled well and could result in conflicts
+          with server code. (Bug #24897)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           The server might fail to use an appropriate index for
           <literal>DELETE</literal> when <literal>ORDER
BY</literal>,
           <literal>LIMIT</literal>, and a non-restricting

@@ -252,6 +269,19 @@
 
       <listitem>
         <para>
+          If an <literal>ORDER BY</literal> or <literal>GROUP
+          BY</literal> list included a constant expression being
+          optimized away and, at the same time, containing single-row
+          subselects that return more that one row, no error was
+          reported. If a query requires sorting by expressions
+          containing single-row subselects that return more than one
+          row, execution of the query may cause a server crash. (Bug
+          #24653)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Attempts to access a <literal>MyISAM</literal> table with a
           corrupt column definition caused a server crash. (Bug #24401)
         </para>


Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml	2007-02-09 18:57:39 UTC (rev 4878)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml	2007-02-09 20:37:09 UTC (rev 4879)
Changed blocks: 2, Lines Added: 25, Lines Deleted: 1; 1694 bytes

@@ -109,6 +109,30 @@
 
       <listitem>
         <para>
+          The arguments of the <literal>ENCODE()</literal> and the
+          <literal>DECODE()</literal> functions were not printed
+          correctly, causing problems in the output of <literal>EXPLAIN
+          EXTENDED</literal> and in view definitions. (Bug #23409)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          An error in the name resolution of nested <literal>JOIN ...
+          USING</literal> constructs was corrected. (Bug #25575)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          A return value of <literal>-1</literal> from user-defined
+          handlers was not handled well and could result in conflicts
+          with server code. (Bug #24897)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           The server might fail to use an appropriate index for
           <literal>DELETE</literal> when <literal>ORDER
BY</literal>,
           <literal>LIMIT</literal>, and a non-restricting

@@ -205,7 +229,7 @@
         <para>
           The <option>--with-readline</option> option for
           <command>configure</command> does not work for commercial
-          source packages, but no error message was printed to that 
+          source packages, but no error message was printed to that
           effect. Now a message is printed. (Bug #25530)
         </para>
       </listitem>


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2007-02-09 18:57:39 UTC (rev 4878)
+++ trunk/refman-5.1/news-5.1.xml	2007-02-09 20:37:09 UTC (rev 4879)
Changed blocks: 1, Lines Added: 32, Lines Deleted: 0; 1527 bytes

@@ -243,6 +243,38 @@
 
       <listitem>
         <para>
+          Indexes disabled with <literal>ALTER TABLE ... DISABLE
+          KEYS</literal> could in some cases be used by specifying
+          <literal>FORCE INDEX</literal>. (Bug #20604)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          The arguments of the <literal>ENCODE()</literal> and the
+          <literal>DECODE()</literal> functions were not printed
+          correctly, causing problems in the output of <literal>EXPLAIN
+          EXTENDED</literal> and in view definitions. (Bug #23409)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          An error in the name resolution of nested <literal>JOIN ...
+          USING</literal> constructs was corrected. (Bug #25575)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          A return value of <literal>-1</literal> from user-defined
+          handlers was not handled well and could result in conflicts
+          with server code. (Bug #24897)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           The server might fail to use an appropriate index for
           <literal>DELETE</literal> when <literal>ORDER
BY</literal>,
           <literal>LIMIT</literal>, and a non-restricting