List:Commits« Previous MessageNext Message »
From:paul Date:January 21 2006 7:01pm
Subject:svn commit - mysqldoc@docsrva: r971 - in trunk: . refman-4.1 refman-5.0 refman-common
View as plain text  
Author: paul
Date: 2006-01-21 20:01:18 +0100 (Sat, 21 Jan 2006)
New Revision: 971

Log:
 r6525@frost:  paul | 2006-01-21 12:39:13 -0600
 Note a DATETIME conversion incompatibility. (Bug#12268)


Modified:
   trunk/
   trunk/refman-4.1/installing.xml
   trunk/refman-5.0/installing.xml
   trunk/refman-common/news-4.1.xml
   trunk/refman-common/news-5.0.xml


Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6524
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2396
   + b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6525
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2396

Modified: trunk/refman-4.1/installing.xml
===================================================================
--- trunk/refman-4.1/installing.xml	2006-01-21 19:01:04 UTC (rev 970)
+++ trunk/refman-4.1/installing.xml	2006-01-21 19:01:18 UTC (rev 971)
@@ -12674,6 +12674,17 @@
 
         <listitem>
           <para>
+            <emphasis role="bold">Incompatible change:</emphasis> Before
+            MySQL 4.1.13, conversion of <literal>DATETIME</literal>
+            values to numeric form by adding zero produced a result in
+            <literal>YYYYMMDDHHMMSS</literal> format. The result of
+            <literal>DATETIME+0</literal> is now in
+            <literal>YYYYMMDDHHMMSS.000000</literal> format.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
             <emphasis role="bold">Incompatible change</emphasis>: Before
             MySQL 4.1.1, the statement parser was less strict and its
             string-to-date conversion would ignore everything up to the

Modified: trunk/refman-5.0/installing.xml
===================================================================
--- trunk/refman-5.0/installing.xml	2006-01-21 19:01:04 UTC (rev 970)
+++ trunk/refman-5.0/installing.xml	2006-01-21 19:01:18 UTC (rev 971)
@@ -12482,6 +12482,17 @@
 
         <listitem>
           <para>
+            <emphasis role="bold">Incompatible change:</emphasis> Before
+            MySQL 4.1.13/5.0.8, conversion of
+            <literal>DATETIME</literal> values to numeric form by adding
+            zero produced a result in <literal>YYYYMMDDHHMMSS</literal>
+            format. The result of <literal>DATETIME+0</literal> is now
+            in <literal>YYYYMMDDHHMMSS.000000</literal> format.
+          </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-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml	2006-01-21 19:01:04 UTC (rev 970)
+++ trunk/refman-common/news-4.1.xml	2006-01-21 19:01:18 UTC (rev 971)
@@ -150,33 +150,36 @@
     For a full list of changes, please refer to the changelog sections
     for each individual 4.1.x release.
   </para>
-  
+
   <section id="news-4-1-18">
+
     <title>&title-news-4-1-18;</title>
 
     <para>
       Functionality added or changed:
     </para>
-    
+
     <itemizedlist>
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: More descriptive warnings are
           now issued when inappropriate logging parameters are set in
           <filename>config.ini</filename>. (Formerly, the warning issued
           was simply <errortext>Could not add logfile
-            destination</errortext>.) (Bug #11331)
-        </para>        
+          destination</errortext>.) (Bug #11331)
+        </para>
       </listitem>
+
     </itemizedlist>
-    
+
     <remark role="todo">
       [js] Uncomment when there are bugfixes to document for this
       release.
     </remark>
+
+<!--
     
-    <!--
-    
     <para>
       Bugs fixed:
     </para>
@@ -190,10 +193,9 @@
     </itemizedlist>
     
       -->
-      
+
   </section>
-  
-  
+
   <section id="news-4-1-17">
 
     <title>&title-news-4-1-17;</title>
@@ -229,7 +231,7 @@
     </para>
 
     <itemizedlist>
-      
+
       <listitem>
         <para>
           <literal>NDBCluster</literal>: Upon the completion of a scan
@@ -2327,7 +2329,18 @@
 
       <listitem>
         <para>
-          Added <option>--add-drop-database</option> option to
+          <emphasis role="bold">Warning: Incompatible change:</emphasis>
+          Previously, conversion of <literal>DATETIME</literal> values
+          to numeric form by adding zero produced a result in
+          <literal>YYYYMMDDHHMMSS</literal> format. The result of
+          <literal>DATETIME+0</literal> is now in
+          <literal>YYYYMMDDHHMMSS.000000</literal> format. (Bug#12268)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Added the <option>--add-drop-database</option> option to
           <literal>mysqldump</literal>. (Bug #3716)
         </para>
       </listitem>
@@ -7742,7 +7755,7 @@
 
       <listitem>
         <para>
-          <emphasis role="bold">Warning: Incompatible change;</emphasis>
+          <emphasis role="bold">Warning: Incompatible change:</emphasis>
           C API change: <literal>mysql_shutdown()</literal> now requires
           a second argument. This is a source-level incompatibility that
           affects how you compile client programs; it does not affect

Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml	2006-01-21 19:01:04 UTC (rev 970)
+++ trunk/refman-common/news-5.0.xml	2006-01-21 19:01:18 UTC (rev 971)
@@ -6198,6 +6198,17 @@
 
       <listitem>
         <para>
+          <emphasis role="bold">Warning: Incompatible change:</emphasis>
+          Previously, conversion of <literal>DATETIME</literal> values
+          to numeric form by adding zero produced a result in
+          <literal>YYYYMMDDHHMMSS</literal> format. The result of
+          <literal>DATETIME+0</literal> is now in
+          <literal>YYYYMMDDHHMMSS.000000</literal> format. (Bug#12268)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <literal>MEMORY</literal> tables now support indexes of up to
           500 bytes. See <xref linkend="memory-storage-engine"/>. (Bug
           #10566)

Thread
svn commit - mysqldoc@docsrva: r971 - in trunk: . refman-4.1 refman-5.0 refman-commonpaul21 Jan