List:Commits« Previous MessageNext Message »
From:paul Date:May 22 2006 8:29pm
Subject:svn commit - mysqldoc@docsrva: r2162 - in trunk: . refman-common
View as plain text  
Author: paul
Date: 2006-05-22 22:29:00 +0200 (Mon, 22 May 2006)
New Revision: 2162

Log:
 r9870@polar:  paul | 2006-05-22 15:32:20 -0500
 Document bugfixes:
 Bug#6951
 Bug#12472
 Bug#13975
 Bug#15137


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


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

Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml	2006-05-22 19:47:08 UTC (rev 2161)
+++ trunk/refman-common/news-5.0.xml	2006-05-22 20:29:00 UTC (rev 2162)
@@ -367,6 +367,31 @@
 
       <listitem>
         <para>
+          The result from <literal>CONV()</literal> is a string, but was
+          not always treated the same way as a string when converted to
+          a real value for an arithmetic operation. (Bug #13975)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>CREATE TABLE ... SELECT ...</literal> statements that
+          used a stored function explicitly or implicitly (through a
+          view) resulted in a <literal>Table not locked</literal> error.
+          (Bug #12472, Bug #15137)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Within a trigger, <literal>SET</literal> used the SQL mode of
+          the invoking statement, not the mode in effect at trigger
+          creation time. (Bug #6951)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           The server no longer uses a signal handler for signal 0
           because it could cause a crash on some platforms. (Bug #15869)
         </para>

Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml	2006-05-22 19:47:08 UTC (rev 2161)
+++ trunk/refman-common/news-5.1.xml	2006-05-22 20:29:00 UTC (rev 2162)
@@ -119,6 +119,31 @@
 
       <listitem>
         <para>
+          The result from <literal>CONV()</literal> is a string, but was
+          not always treated the same way as a string when converted to
+          a real value for an arithmetic operation. (Bug #13975)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>CREATE TABLE ... SELECT ...</literal> statements that
+          used a stored function explicitly or implicitly (through a
+          view) resulted in a <literal>Table not locked</literal> error.
+          (Bug #12472, Bug #15137)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Within a trigger, <literal>SET</literal> used the SQL mode of
+          the invoking statement, not the mode in effect at trigger
+          creation time. (Bug #6951)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           The server no longer uses a signal handler for signal 0
           because it could cause a crash on some platforms. (Bug #15869)
         </para>

Thread
svn commit - mysqldoc@docsrva: r2162 - in trunk: . refman-commonpaul22 May