svn commit - mysqldoc@docsrva: r6804 - in trunk: refman-5.0 refman-5.1 userguide

[plavin]

Author: plavin
Date: 2007-06-15 15:35:05 +0200 (Fri, 15 Jun 2007)
New Revision: 6804

Log:
Document bugs 28929 and 28980.


Modified:
   trunk/refman-5.0/data-types.xml
   trunk/refman-5.0/releasenotes-es-5.0.xml
   trunk/refman-5.1/data-types.xml
   trunk/refman-5.1/news-5.1.xml
   trunk/userguide/mysql-client-programs.xml


Modified: trunk/refman-5.0/data-types.xml
===================================================================
--- trunk/refman-5.0/data-types.xml	2007-06-15 12:02:21 UTC (rev 6803)
+++ trunk/refman-5.0/data-types.xml	2007-06-15 13:35:05 UTC (rev 6804)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 1055 bytes

@@ -2630,11 +2630,11 @@
       Prior to MySQL 5.0.42, when <literal>DATE</literal>
       values are compared with <literal>DATETIME</literal> values
       the time portion of the <literal>DATETIME</literal> value is
-      ignored. Starting from MySQL 5.0.42 a 
+      ignored. Starting from MySQL 5.0.42, a 
       <literal>DATE</literal> value is coerced to the        
       <literal>DATETIME</literal> type by adding the time portion 
-      as  <literal>'00:00:00'</literal>. To mimic the old behavior 
-      use the CAST() function in the following way:
+      as <literal>'00:00:00'</literal>. To mimic the old behavior 
+      use the <literal>CAST()</literal> function in the following way:
       <literal>SELECT <replaceable>date_field</replaceable> = 
         CAST(NOW() as DATE);</literal>.
     </para>


Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml	2007-06-15 12:02:21 UTC (rev 6803)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml	2007-06-15 13:35:05 UTC (rev 6804)
Changed blocks: 1, Lines Added: 10, Lines Deleted: 0; 765 bytes

@@ -96,6 +96,16 @@
           or DDL statements on the target table. (Bug #23667)
         </para>
       </listitem>
+      
+      <listitem>
+        <para>
+          Using an <literal>INTEGER</literal> column from a table to 
+          <literal>ROUND()</literal> a number produced different
+          results than using a constant with the same value
+          as the <literal>INTEGER</literal> column.
+          (Bug# 28980)
+        </para>
+      </listitem>
 
       <listitem>
         <para>


Modified: trunk/refman-5.1/data-types.xml
===================================================================
--- trunk/refman-5.1/data-types.xml	2007-06-15 12:02:21 UTC (rev 6803)
+++ trunk/refman-5.1/data-types.xml	2007-06-15 13:35:05 UTC (rev 6804)
Changed blocks: 1, Lines Added: 13, Lines Deleted: 0; 1099 bytes

@@ -2498,6 +2498,19 @@
       to allow zero in dates, you can use the
       <literal>NO_ZERO_IN_DATE</literal> SQL mode).
     </para>
+    
+    <para>
+      Prior to MySQL 5.1.18, when <literal>DATE</literal>
+      values are compared with <literal>DATETIME</literal> values
+      the time portion of the <literal>DATETIME</literal> value is
+      ignored. Starting from MySQL 5.1.18, a 
+      <literal>DATE</literal> value is coerced to the        
+      <literal>DATETIME</literal> type by adding the time portion 
+      as <literal>'00:00:00'</literal>. To mimic the old behavior 
+      use the <literal>CAST()</literal> function in the following way:
+      <literal>SELECT <replaceable>date_field</replaceable> = 
+       CAST(NOW() as DATE);</literal>.
+     </para>
 
     <para>
       MySQL also allows you to store <literal>'0000-00-00'</literal> as


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2007-06-15 12:02:21 UTC (rev 6803)
+++ trunk/refman-5.1/news-5.1.xml	2007-06-15 13:35:05 UTC (rev 6804)
Changed blocks: 2, Lines Added: 24, Lines Deleted: 0; 1579 bytes

@@ -160,6 +160,16 @@
       
       <listitem>
         <para>
+          Using an <literal>INTEGER</literal> column from a table to 
+          <literal>ROUND()</literal> a number produced different
+          results than using a constant with the same value
+          as the <literal>INTEGER</literal> column.
+          (Bug# 28980)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
           The <literal>PARTITION_COMMENT</literal> column of the
           <literal>INFORMATION_SCHEMA.PARTITIONS</literal> table had the
           wrong default value. (Bug #28007)

@@ -1397,6 +1407,20 @@
     </para>
 
     <itemizedlist>
+      
+      <listitem>
+        <para>
+          Prior to this release, when <literal>DATE</literal> values
+          were compared with <literal>DATETIME</literal> values the time
+          portion of the <literal>DATETIME</literal> value was ignored.
+          Now a <literal>DATE</literal> value is coerced to the
+          <literal>DATETIME</literal> type by adding the time portion as
+          <quote>00:00:00</quote>. To mimic the old behavior use the
+          CAST() function in the following way: <literal>SELECT
+            <replaceable>date_field</replaceable> = CAST(NOW() as
+            DATE);</literal>. (Bug# 28929)
+        </para>
+      </listitem>
 
       <listitem>
         <para>


Modified: trunk/userguide/mysql-client-programs.xml
===================================================================
--- trunk/userguide/mysql-client-programs.xml	2007-06-15 12:02:21 UTC (rev 6803)
+++ trunk/userguide/mysql-client-programs.xml	2007-06-15 13:35:05 UTC (rev 6804)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 587 bytes

@@ -923,7 +923,7 @@
         <para>
           To restart the server on Unix [and Mac] systems issue the
           command, <command>mysqld_safe</command> and on Windows,
-          <command>mysqld</command> (?).
+          <command>mysqld</command> (?). For more information ...
         </para>
 
       </section>