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

[paul]

Author: paul
Date: 2007-02-08 19:47:15 +0100 (Thu, 08 Feb 2007)
New Revision: 4866

Log:
 r19601@polar:  paul | 2007-02-08 12:46:21 -0600
 Document bugfixes:
 Bug#17711
 Bug#23299
 Bug#25044
 Bug#25123
 Bug#25407
 Bug#25551
 Bug#25580


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:19599
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:16016
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:19601
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:16016
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-08 17:56:07 UTC (rev 4865)
+++ trunk/refman-4.1/news-4.1.xml	2007-02-08 18:47:15 UTC (rev 4866)
Changed blocks: 1, Lines Added: 26, Lines Deleted: 0; 1318 bytes

@@ -226,6 +226,32 @@
 
       <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
+          <literal>WHERE</literal> are present. (Bug #17711)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          For <literal>BOOLEAN</literal> mode full-text searches on
+          non-indexed columns, <literal>NULL</literal> rows generated by
+          a <literal>LEFT JOIN</literal> caused incorrect query results.
+          (Bug #25637; see also Bug #14708)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>SHOW COLUMNS</literal> reported some <literal>NOT
+          NULL</literal> columns as <literal>NULL</literal>. (Bug
+          #22377)
+        </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-08 17:56:07 UTC (rev 4865)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml	2007-02-08 18:47:15 UTC (rev 4866)
Changed blocks: 1, Lines Added: 67, Lines Deleted: 0; 2749 bytes

@@ -109,6 +109,73 @@
 
       <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
+          <literal>WHERE</literal> are present. (Bug #17711)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Use of <literal>ON DUPLICATE KEY UPDATE</literal> defeated the
+          usual restriction against inserting into a join-based view
+          unless only one of the underlying tables is used. (Bug #25123)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Some queries against <literal>INFORMATION_SCHEMA</literal>
+          that used subqueries failed. (Bug #23299).
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>SHOW COLUMNS</literal> reported some <literal>NOT
+          NULL</literal> columns as <literal>NULL</literal>. (Bug
+          #22377)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          View definitions that used the <literal>!</literal> operator
+          were treated as containing the <literal>NOT</literal>
+          operator, which has a different precedence and can produce
+          different results. (Bug #25580).
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          For a <literal>UNIQUE</literal> index containing many
+          <literal>NULL</literal> values, the optimizer would prefer the
+          index for <literal><replaceable>col</replaceable> IS
+          NULL</literal> conditions over other more selective indexes.
+          (Bug #25407).
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>GROUP BY</literal> and
<literal>DISTINCT</literal>
+          did not group <literal>NULL</literal> values for columns that
+          have a <literal>UNIQUE</literal> index. (Bug #25551).
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>ALTER TABLE ... ENABLE KEYS</literal> acquired a
+          global lock, preventing concurrent execution of other
+          statements that use tables. (Bug #25044).
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           For an <literal>InnoDB</literal> table with any <literal>ON
           DELETE</literal> trigger, <literal>TRUNCATE TABLE</literal>
           mapped to <literal>DELETE</literal> and activated triggers.


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2007-02-08 17:56:07 UTC (rev 4865)
+++ trunk/refman-5.1/news-5.1.xml	2007-02-08 18:47:15 UTC (rev 4866)
Changed blocks: 2, Lines Added: 67, Lines Deleted: 0; 2927 bytes

@@ -243,6 +243,65 @@
 
       <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
+          <literal>WHERE</literal> are present. (Bug #17711)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Use of <literal>ON DUPLICATE KEY UPDATE</literal> defeated the
+          usual restriction against inserting into a join-based view
+          unless only one of the underlying tables is used. (Bug #25123)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          View definitions that used the <literal>!</literal> operator
+          were treated as containing the <literal>NOT</literal>
+          operator, which has a different precedence and can produce
+          different results. (Bug #25580).
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Some queries against <literal>INFORMATION_SCHEMA</literal>
+          that used subqueries failed. (Bug #23299).
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          For a <literal>UNIQUE</literal> index containing many
+          <literal>NULL</literal> values, the optimizer would prefer the
+          index for <literal><replaceable>col</replaceable> IS
+          NULL</literal> conditions over other more selective indexes.
+          (Bug #25407).
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>GROUP BY</literal> and
<literal>DISTINCT</literal>
+          did not group <literal>NULL</literal> values for columns that
+          have a <literal>UNIQUE</literal> index. (Bug #25551).
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>ALTER TABLE ... ENABLE KEYS</literal> acquired a
+          global lock, preventing concurrent execution of other
+          statements that use tables. (Bug #25044).
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           For an <literal>InnoDB</literal> table with any <literal>ON
           DELETE</literal> trigger, <literal>TRUNCATE TABLE</literal>
           mapped to <literal>DELETE</literal> and activated triggers.

@@ -666,6 +725,14 @@
 
       <listitem>
         <para>
+          <literal>SHOW COLUMNS</literal> reported some <literal>NOT
+          NULL</literal> columns as <literal>NULL</literal>. (Bug
+          #22377)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Attempts to access a <literal>MyISAM</literal> table with a
           corrupt column definition caused a server crash. (Bug #24401)
         </para>