svn commit - mysqldoc@docsrva: r1421 - trunk/refman-common

[mhillyer]

Author: mhillyer
Date: 2006-02-21 23:37:04 +0100 (Tue, 21 Feb 2006)
New Revision: 1421

Log:
Document bugfixes: 16591,16260,16203,14927,16272

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-02-21 22:32:38 UTC (rev 1420)
+++ trunk/refman-common/news-4.1.xml	2006-02-21 22:37:04 UTC (rev 1421)
@@ -155,11 +155,6 @@
 
     <title>&title-news-4-1-19;</title>
 
-    <remark role="todo">
-      [js] Uncomment following once we have some feature changes to
-      report for 4.1.19.
-    </remark>
-
     <para>
       Functionality added or changed:
     </para>
@@ -187,6 +182,16 @@
 
       <listitem>
         <para>
+          A statement containing <literal>GROUP BY</literal> and
+          <literal>HAVING</literal> clauses could return incorrect
+          results when the <literal>HAVING</literal> clause contained
+          logic that returned <literal>FALSE</literal> for every row.
+          (Bug #14927)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <command>mysqldump</command> tried to dump data from a view.
           (In MySQL 4.1, this applies when connecting to a server from
           MySQL 5.0 or higher.) (Bug #16389)

Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml	2006-02-21 22:32:38 UTC (rev 1420)
+++ trunk/refman-common/news-5.0.xml	2006-02-21 22:37:04 UTC (rev 1421)
@@ -325,6 +325,39 @@
 
       <listitem>
         <para>
+          MySQL server dropped client connection for certain SELECT
+          statements against views defined that used
+          <literal>MERGE</literal> algorithm. (Bug #16260)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          A call to the <function>IF()</function> function using decimal
+          arguments could return incorrect results. (Bug #16272)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          A statement containing <literal>GROUP BY</literal> and
+          <literal>HAVING</literal> clauses could return incorrect
+          results when the <literal>HAVING</literal> clause contained
+          logic that returned <literal>FALSE</literal> for every row.
+          (Bug #14927)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Using <literal>GROUP BY</literal> on column used in
+          <literal>WHERE</literal> clause could cause empty set to be
+          returned. (Bug #16203)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           For a MySQL 5.0 server, using MySQL 4.1 tables in queries with
           a <literal>GROUP BY</literal> clause could result in buffer
           overrun or a server crash. (Bug #16752)

Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml	2006-02-21 22:32:38 UTC (rev 1420)
+++ trunk/refman-common/news-5.1.xml	2006-02-21 22:37:04 UTC (rev 1421)
@@ -186,6 +186,39 @@
 
       <listitem>
         <para>
+          Querying the <literal>INFORMATION_SCHEMA.partitions</literal>
+          table on a non-max server caused a server crash. (Bug #16591)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          MySQL server dropped client connection for certain SELECT
+          statements against views defined that used
+          <literal>MERGE</literal> algorithm. (Bug #16260)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          A statement containing <literal>GROUP BY</literal> and
+          <literal>HAVING</literal> clauses could return incorrect
+          results when the <literal>HAVING</literal> clause contained
+          logic that returned <literal>FALSE</literal> for every row.
+          (Bug #14927)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Using <literal>GROUP BY</literal> on column used in
+          <literal>WHERE</literal> clause could cause empty set to be
+          returned. (Bug #16203)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <literal>DROP DATABASE</literal> did not drop events for the
           database. (Bug #16406)
         </para>