MySQL Lists are EOL. Please join:

List:Commits« Previous MessageNext Message »
From:paul Date:April 24 2007 1:44am
Subject:svn commit - mysqldoc@docsrva: r6098 - in trunk: . refman-4.1 refman-5.0 refman-5.1
View as plain text  
Author: paul
Date: 2007-04-24 03:44:45 +0200 (Tue, 24 Apr 2007)
New Revision: 6098

Log:
 r19558@frost:  paul | 2007-04-23 20:41:58 -0500
 Document bugfixes:
 Bug#18997
 Bug#21103
 Bug#24778
 Bug#26121
 Bug#26624
 Bug#27171
 Bug#27354
 Bug#27583
 Bug#27733
 Bug#27870


Modified:
   trunk/refman-4.1/news-4.1.xml
   trunk/refman-5.0/releasenotes-es-5.0.xml
   trunk/refman-5.1/installing.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:23915
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:19497
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:14593
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:23915
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:19558
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:14593


Modified: trunk/refman-4.1/news-4.1.xml
===================================================================
--- trunk/refman-4.1/news-4.1.xml	2007-04-24 00:29:01 UTC (rev 6097)
+++ trunk/refman-4.1/news-4.1.xml	2007-04-24 01:44:45 UTC (rev 6098)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 0; 726 bytes

@@ -296,6 +296,14 @@
 
       <listitem>
         <para>
+          The range optimizer could consume a combinatorial amount of
+          memory for certain classes of <literal>WHERE</literal>
+          clauses. (Bug #26624)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Conversion of <literal>DATETIME</literal> values in numeric
           contexts sometimes did not produce a double
           (<literal>YYYYMMDDHHMMSS.uuuuuu</literal>) value. (Bug #16546)


Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml	2007-04-24 00:29:01 UTC (rev 6097)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml	2007-04-24 01:44:45 UTC (rev 6098)
Changed blocks: 5, Lines Added: 83, Lines Deleted: 3; 3574 bytes

@@ -31,9 +31,9 @@
     <filename>refman-common</filename> directory.
   </remark>
 
-  <section id="releasenotes-es-5-0-40">
+  <section id="releasenotes-es-5-0-42">
 
-    <title>Release Notes for MySQL Enterprise 5.0.40 (Not yet released)</title>
+    <title>Release Notes for MySQL Enterprise 5.0.42 (Not yet released)</title>
 
     <para role="release-level">
       This is a <emphasis>Monthly Rapid Update</emphasis> release of the

@@ -42,7 +42,7 @@
 
     <para>
       This section documents all changes and bug fixes that have been
-      applied since the last MySQL Enterprise Server release (5.0.38).
+      applied since the last MySQL Enterprise Server release (5.0.40).
     </para>
 
     <remark>

@@ -50,6 +50,7 @@
       document.
     </remark>
 
+<!--
     <para>
       Functionality added or changed:
     </para>

@@ -58,6 +59,77 @@
 
       <listitem>
         <para>
+        </para>
+      </listitem>
+
+    </itemizedlist>
+-->
+
+    <para>
+      Bugs fixed:
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          <command>mysqlbinlog</command> produced different output with
+          the <option>-R</option> option than without it. (Bug #27171)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          A stored function invocation in the <literal>WHERE</literal>
+          clause was treated as a constant. (Bug #27354)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Some equi-joins containing a <literal>WHERE</literal> clause
+          that included a <literal>NOT IN</literal> subquery caused a
+          server crash. (Bug #27870)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          For queries that used <literal>ORDER BY</literal> with
+          <literal>InnoDB</literal> tables, if the optimizer chose an
+          index for accessing the table but found a covering index that
+          enabled the <literal>ORDER BY</literal> to be skipped, no
+          results were returned. (Bug #24778)
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
+  </section>
+
+  <section id="releasenotes-es-5-0-40">
+
+    <title>Release Notes for MySQL Enterprise 5.0.40 (Not yet released)</title>
+
+    <para role="release-level">
+      This is a <emphasis>Monthly Rapid Update</emphasis> release of the
+      MySQL Enterprise Server 5.0.
+    </para>
+
+    <para>
+      This section documents all changes and bug fixes that have been
+      applied since the last MySQL Enterprise Server release (5.0.38).
+    </para>
+
+
+    <para>
+      Functionality added or changed:
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
           Prefix lengths for columns in <literal>SPATIAL</literal>
           indexes are no longer displayed in <literal>SHOW CREATE
           TABLE</literal> output. <command>mysqldump</command> uses that

@@ -348,6 +420,14 @@
 
       <listitem>
         <para>
+          The range optimizer could consume a combinatorial amount of
+          memory for certain classes of <literal>WHERE</literal>
+          clauses. (Bug #26624)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Conversion of <literal>DATETIME</literal> values in numeric
           contexts sometimes did not produce a double
           (<literal>YYYYMMDDHHMMSS.uuuuuu</literal>) value. (Bug #16546)


Modified: trunk/refman-5.1/installing.xml
===================================================================
--- trunk/refman-5.1/installing.xml	2007-04-24 00:29:01 UTC (rev 6097)
+++ trunk/refman-5.1/installing.xml	2007-04-24 01:44:45 UTC (rev 6098)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 15; 1221 bytes

@@ -12741,21 +12741,6 @@
 
         <listitem>
           <para>
-            For dates with 4-digit year parts less than 200, an implicit
-            conversion to add a century was applied for date arithmetic
-            performed with <literal>DATE_ADD()</literal>,
-            <literal>DATE_SUB()</literal>, <literal>+
-            INTERVAL</literal>, and <literal>- INTERVAL</literal>. (For
-            example, <literal>DATE_ADD('0050-01-01 00:00:00', INTERVAL 0
-            SECOND)</literal> became <literal>'2050-01-01
-            00:00:00'</literal>.) As of MySQL 5.1.11, these operations
-            return <literal>NULL</literal> rather than an incorrect
-            non-<literal>NULL</literal> value. (Bug #18997)
-          </para>
-        </listitem>
-
-        <listitem>
-          <para>
             Some keywords are reserved in MySQL &current-series; that
             were not reserved in MySQL &previous-series;. See
             <xref linkend="reserved-words"/>.


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2007-04-24 00:29:01 UTC (rev 6097)
+++ trunk/refman-5.1/news-5.1.xml	2007-04-24 01:44:45 UTC (rev 6098)
Changed blocks: 1, Lines Added: 100, Lines Deleted: 0; 3979 bytes

@@ -467,6 +467,106 @@
 
       <listitem>
         <para>
+          The range optimizer could consume a combinatorial amount of
+          memory for certain classes of <literal>WHERE</literal>
+          clauses. (Bug #26624)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <command>mysqlbinlog</command> produced different output with
+          the <option>-R</option> option than without it. (Bug #27171)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          A stored function invocation in the <literal>WHERE</literal>
+          clause was treated as a constant. (Bug #27354)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <command>mysqldump</command> could not dump the log tables.
+          (Bug #26121)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Implicit conversion of <literal>9912101</literal> to
+          <literal>DATE</literal> did not match <literal>CAST(9912101 AS
+          DATE)</literal>. (Bug #23093)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>CURDATE()</literal> is less than
+          <literal>NOW()</literal>, either when comparing
+          <literal>CURDATE()</literal> directly (<literal>CURDATE() &lt;
+          NOW()</literal> is true) or when casting
+          <literal>CURDATE()</literal> to <literal>DATE</literal>
+          (<literal>CAST(CURDATE() AS DATE) &lt; NOW()</literal> is
+          true). However, storing <literal>CURDATE()</literal> in a
+          <literal>DATE</literal> column and comparing
+          <literal><replaceable>col_name</replaceable> &lt;
+          NOW()</literal> incorrectly yielded false. This is fixed by
+          comparing a <literal>DATE</literal> column as
+          <literal>DATETIME</literal> for comparisons to a
+          <literal>DATETIME</literal> constant. (Bug #21103)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          For dates with 4-digit year parts less than 200, an incorrect
+          implicit conversion to add a century was applied for date
+          arithmetic performed with <literal>DATE_ADD()</literal>,
+          <literal>DATE_SUB()</literal>, <literal>+ INTERVAL</literal>,
+          and <literal>- INTERVAL</literal>. (For example,
+          <literal>DATE_ADD('0050-01-01 00:00:00', INTERVAL 0
+          SECOND)</literal> became <literal>'2050-01-01
+          00:00:00'</literal>.) (Bug #18997)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Some equi-joins containing a <literal>WHERE</literal> clause
+          that included a <literal>NOT IN</literal> subquery caused a
+          server crash. (Bug #27870)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          A memory leak in the event scheduler that was uncovered by
+          Valgrind was fixed. (Bug #27733)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          For queries that used <literal>ORDER BY</literal> with
+          <literal>InnoDB</literal> tables, if the optimizer chose an
+          index for accessing the table but found a covering index that
+          enabled the <literal>ORDER BY</literal> to be skipped, no
+          results were returned. (Bug #24778)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Group relay log rotation updated only the log position and not
+          the name, causing the slave to stop. (Bug #27583)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Conversion of <literal>DATETIME</literal> values in numeric
           contexts sometimes did not produce a double
           (<literal>YYYYMMDDHHMMSS.uuuuuu</literal>) value. (Bug #16546)


Thread
svn commit - mysqldoc@docsrva: r6098 - in trunk: . refman-4.1 refman-5.0 refman-5.1paul24 Apr