svn commit - mysqldoc@docsrva: r2210 - in trunk: . refman-5.1 refman-common

[paul]

Author: paul
Date: 2006-05-26 16:30:32 +0200 (Fri, 26 May 2006)
New Revision: 2210

Log:
 r10754@frost:  paul | 2006-05-26 08:57:14 -0500
 Document bugfix. (Bug#18997)


Modified:
   trunk/
   trunk/refman-5.1/installing.xml
   trunk/refman-common/news-5.1.xml


Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:10054
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:10691
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:7517
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:10054
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:10754
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:7517

Modified: trunk/refman-5.1/installing.xml
===================================================================
--- trunk/refman-5.1/installing.xml	2006-05-26 00:05:54 UTC (rev 2209)
+++ trunk/refman-5.1/installing.xml	2006-05-26 14:30:32 UTC (rev 2210)
@@ -12255,6 +12255,21 @@
 
         <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-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml	2006-05-26 00:05:54 UTC (rev 2209)
+++ trunk/refman-common/news-5.1.xml	2006-05-26 14:30:32 UTC (rev 2210)
@@ -57,7 +57,7 @@
     </para>
 
     <itemizedlist>
-      
+
       <listitem>
         <para>
           Added the <literal>SHOW CONTRIBUTORS</literal> statement.
@@ -110,7 +110,7 @@
     </para>
 
     <itemizedlist>
-      
+
       <listitem>
         <para>
           <emphasis role="bold">Incompatible change</emphasis>: The
@@ -121,10 +121,10 @@
           Scheduler thread can be no longer be activated or deactivated
           at run time. (Bug #17619)
         </para>
-        
+
         <para>
-          For more information regarding these changes, see 
-          <xref linkend="events-overview"/>. 
+          For more information regarding these changes, see
+          <xref linkend="events-overview"/>.
         </para>
       </listitem>
 
@@ -221,16 +221,31 @@
     </para>
 
     <itemizedlist>
-      
+
       <para>
         <literal>NDB Cluster</literal>: <literal>SELECT
-          MIN(<replaceable>unique_column</replaceable>)</literal> from a
+        MIN(<replaceable>unique_column</replaceable>)</literal> from a
         Cluster table with user-defined partitioning crashed the server.
         (Bug #18730)
       </para>
 
       <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>.) Now these operations return
+          <literal>NULL</literal> rather than an incorrect
+          non-<literal>NULL</literal> value. (Bug #18997)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <literal>BLOB</literal> or <literal>TEXT</literal> arguments
           to or values returned from stored functions were not copied
           properly if too long and could become garbled. (Bug #18587)
@@ -243,14 +258,14 @@
           one another could crash the server. (Bug #16428)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           In was not possible to invoke a stored routine containing
           dynamic SQL from a scheduled event. (Bug #19264)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: Running <literal>ALL