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

[paul]

Author: paul
Date: 2006-10-24 23:23:53 +0200 (Tue, 24 Oct 2006)
New Revision: 3726

Log:
 r11224@frost:  paul | 2006-10-24 16:23:00 -0500
 Document bugfix#14654


Modified:
   trunk/refman-5.0/news-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:14819
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:11200
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:10957
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:14819
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:11224
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:10957


Modified: trunk/refman-5.0/news-5.0.xml
===================================================================
--- trunk/refman-5.0/news-5.0.xml	2006-10-24 19:23:05 UTC (rev 3725)
+++ trunk/refman-5.0/news-5.0.xml	2006-10-24 21:23:53 UTC (rev 3726)
Changed blocks: 1, Lines Added: 16, Lines Deleted: 0; 1245 bytes

@@ -506,6 +506,22 @@
 
       <listitem>
         <para>
+          The parser rejected queries that selected from a table twice
+          using a <literal>UNION</literal> within a subquery. The parser
+          now supports arbitrary subquery, join, and parenthesis
+          operations within <literal>EXISTS</literal> subqueries. A
+          limitation still exists for scalar subqueries: If the subquery
+          contains <literal>UNION</literal>, the first
+          <literal>SELECT</literal> of the
<literal>UNION</literal>
+          cannot be within parentheses. For example, <literal>SELECT
+          (SELECT a FROM t1 UNION SELECT b FROM t2)</literal> will work,
+          but <literal>SELECT ((SELECT a FROM t1) UNION (SELECT b FROM
+          t2))</literal> will not. (Bug #14654)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Subqueries with aggregate functions but no
           <literal>FROM</literal> clause could return incorrect results.
           (Bug #21540)


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2006-10-24 19:23:05 UTC (rev 3725)
+++ trunk/refman-5.1/news-5.1.xml	2006-10-24 21:23:53 UTC (rev 3726)
Changed blocks: 2, Lines Added: 29, Lines Deleted: 13; 2686 bytes

@@ -931,6 +931,35 @@
 
       <listitem>
         <para>
+          Deleting entries from a large <literal>MyISAM</literal> index
+          could cause index corruption when it needed to shrink. Deletes
+          from an index can happen when a record is deleted, when a key
+          changes and must be moved, and when a key must be un-inserted
+          because of a duplicate key. This can also happen in
+          <literal>REPAIR TABLE</literal> when a duplicate key is found
+          and in <command>myisamchk</command> when sorting the records
+          by an index. (Bug #22384)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          The parser rejected queries that selected from a table twice
+          using a <literal>UNION</literal> within a subquery. The parser
+          now supports arbitrary subquery, join, and parenthesis
+          operations within <literal>EXISTS</literal> subqueries. A
+          limitation still exists for scalar subqueries: If the subquery
+          contains <literal>UNION</literal>, the first
+          <literal>SELECT</literal> of the
<literal>UNION</literal>
+          cannot be within parentheses. For example, <literal>SELECT
+          (SELECT a FROM t1 UNION SELECT b FROM t2)</literal> will work,
+          but <literal>SELECT ((SELECT a FROM t1) UNION (SELECT b FROM
+          t2))</literal> will not. (Bug #14654)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Incorrect type aggregation for <literal>IN</literal> and
           <literal>CASE</literal> expressions could lead to an incorrect
           result. (Bug #18360)

@@ -948,19 +977,6 @@
 
       <listitem>
         <para>
-          Deleting entries from a large <literal>MyISAM</literal> index
-          could cause index corruption when it needed to shrink. Deletes
-          from an index can happen when a record is deleted, when a key
-          changes and must be moved, and when a key must be un-inserted
-          because of a duplicate key. This can also happen in
-          <literal>REPAIR TABLE</literal> when a duplicate key is found
-          and in <command>myisamchk</command> when sorting the records
-          by an index. (Bug #22384)
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
           The optimizer did not take advantage of indexes on columns
           used for the second or third arguments of
           <literal>BETWEEN</literal>. (Bug #18165)