List:Commits« Previous MessageNext Message »
From:paul Date:January 24 2007 10:29pm
Subject:svn commit - mysqldoc@docsrva: r4630 - in trunk: . refman-4.1 refman-5.0 refman-5.1
View as plain text  
Author: paul
Date: 2007-01-24 22:29:57 +0100 (Wed, 24 Jan 2007)
New Revision: 4630

Log:
 r15249@frost:  paul | 2007-01-24 15:29:14 -0600
 Documented bugfixes:
 Bug#15439
 Bug#20061
 Bug#21328
 Bug#22646
 Bug#23404
 Bug#24293
 Bug#25027
 Bug#25106
 Bug#25396


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


Modified: trunk/refman-4.1/functions.xml
===================================================================
--- trunk/refman-4.1/functions.xml	2007-01-24 19:21:36 UTC (rev 4629)
+++ trunk/refman-4.1/functions.xml	2007-01-24 21:29:57 UTC (rev 4630)
Changed blocks: 1, Lines Added: 9, Lines Deleted: 0; 811 bytes

@@ -6991,6 +6991,15 @@
           (<xref linkend="locale-support"/>).
         </para>
 
+        <para>
+          As of MySQL 4.1.23, <literal>DATE_FORMAT()</literal> returns a
+          string with a character set and collation given by
+          <literal>character_set_connection</literal> and
+          <literal>collation_connection</literal> so that it can return
+          month and weekday names containing non-ASCII characters.
+          Before 4.1.23, the return value is a binary string.
+        </para>
+
         <remark role="help-example"/>
 
 <programlisting>


Modified: trunk/refman-4.1/news-4.1.xml
===================================================================
--- trunk/refman-4.1/news-4.1.xml	2007-01-24 19:21:36 UTC (rev 4629)
+++ trunk/refman-4.1/news-4.1.xml	2007-01-24 21:29:57 UTC (rev 4630)
Changed blocks: 2, Lines Added: 29, Lines Deleted: 0; 1739 bytes

@@ -173,6 +173,19 @@
 
       <listitem>
         <para>
+          <emphasis role="bold">Incompatible change</emphasis>:
+          Previously, the <literal>DATE_FORMAT()</literal> function
+          returned a binary string. Now it returns a string with a
+          character set and collation given by
+          <literal>character_set_connection</literal> and
+          <literal>collation_connection</literal> so that it can return
+          month and weekday names containing non-ASCII characters. (Bug
+          #22646)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <emphasis role="bold">Incompatible change</emphasis>: The
           <literal>prepared_stmt_count</literal> system variable has
           been converted to the <literal>Prepared_stmt_count</literal>

@@ -211,6 +224,22 @@
 
       <listitem>
         <para>
+          A table created with the <literal>ROW_FORMAT = FIXED</literal>
+          table option loses the option if an index is added or dropped
+          with <literal>CREATE INDEX</literal> or <literal>DROP
+          INDEX</literal>. (Bug #23404)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          The <command>BUILD/check-cpu</command> script did not
+          recognize Celeron processors. (Bug #20061)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <literal>InnoDB</literal> showed substandard performance with
           multiple queries running concurrently. (Bug #15815)
         </para>


Modified: trunk/refman-5.0/functions.xml
===================================================================
--- trunk/refman-5.0/functions.xml	2007-01-24 19:21:36 UTC (rev 4629)
+++ trunk/refman-5.0/functions.xml	2007-01-24 21:29:57 UTC (rev 4630)
Changed blocks: 1, Lines Added: 9, Lines Deleted: 0; 811 bytes

@@ -7095,6 +7095,15 @@
           (<xref linkend="locale-support"/>).
         </para>
 
+        <para>
+          As of MySQL 5.0.36, <literal>DATE_FORMAT()</literal> returns a
+          string with a character set and collation given by
+          <literal>character_set_connection</literal> and
+          <literal>collation_connection</literal> so that it can return
+          month and weekday names containing non-ASCII characters.
+          Before 5.0.36, the return value is a binary string.
+        </para>
+
         <remark role="help-example"/>
 
 <programlisting>


Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml	2007-01-24 19:21:36 UTC (rev 4629)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml	2007-01-24 21:29:57 UTC (rev 4630)
Changed blocks: 5, Lines Added: 68, Lines Deleted: 5; 3626 bytes

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

@@ -64,11 +63,19 @@
     <itemizedlist>
 
       <listitem>
-        <para></para>
+        <para>
+          <emphasis role="bold">Incompatible change</emphasis>:
+          Previously, the <literal>DATE_FORMAT()</literal> function
+          returned a binary string. Now it returns a string with a
+          character set and collation given by
+          <literal>character_set_connection</literal> and
+          <literal>collation_connection</literal> so that it can return
+          month and weekday names containing non-ASCII characters. (Bug
+          #22646)
+        </para>
       </listitem>
 
     </itemizedlist>
--->
 
     <para>
       Bugs fixed:

@@ -78,6 +85,13 @@
 
       <listitem>
         <para>
+          The <command>BUILD/check-cpu</command> script did not
+          recognize Celeron processors. (Bug #20061)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           On Windows, the <literal>SLEEP()</literal> function could
           sleep too long, especially after a change to the system clock.
           (Bug #14094, Bug #17635)

@@ -216,6 +230,55 @@
 
       <listitem>
         <para>
+          Using a view in combination with a <literal>USING</literal>
+          clause caused column aliases to be ignored. (Bug #25106)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          A view was not handled correctly if the
+          <literal>SELECT</literal> part contained
+          &lsquo;<literal>\Z</literal>&rsquo;. (Bug #24293)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Inserting a row into a table without specifying a value for a
+          <literal>BINARY(<replaceable>N</replaceable>) NOT
+          NULL</literal> column caused the column to be set to spaces,
+          not zeroes. (Bug #14171)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          An assertion failed incorrectly for prepared statements that
+          contained a single-row non-correlated subquery that was used
+          as an argument of the IS NULL predicate. (Bug #25027)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          A table created with the <literal>ROW_FORMAT = FIXED</literal>
+          table option loses the option if an index is added or dropped
+          with <literal>CREATE INDEX</literal> or <literal>DROP
+          INDEX</literal>. (Bug #23404)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Dropping a user-defined function sometimes did not remove the
+          UDF entry from the <literal>mysql.proc</literal> table. (Bug
+          #15439)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Changing the value of <literal>MI_KEY_BLOCK_LENGTH</literal>
           in <filename>myisam.h</filename> and recompiling MySQL
           resulted in a <command>myisamchk</command> that saw existing

@@ -1209,8 +1272,8 @@
     <title>Release Notes for MySQL Enterprise 5.0.30sp1 (19 January
2007)</title>
 
     <para role="release-level">
-      This is a <emphasis>Service Pack</emphasis> release of the
-      MySQL Enterprise Server 5.0.
+      This is a <emphasis>Service Pack</emphasis> release of the MySQL
+      Enterprise Server 5.0.
     </para>
 
     <para>


Modified: trunk/refman-5.1/functions.xml
===================================================================
--- trunk/refman-5.1/functions.xml	2007-01-24 19:21:36 UTC (rev 4629)
+++ trunk/refman-5.1/functions.xml	2007-01-24 21:29:57 UTC (rev 4630)
Changed blocks: 1, Lines Added: 9, Lines Deleted: 0; 811 bytes

@@ -7048,6 +7048,15 @@
           (<xref linkend="locale-support"/>).
         </para>
 
+        <para>
+          As of MySQL 5.1.15, <literal>DATE_FORMAT()</literal> returns a
+          string with a character set and collation given by
+          <literal>character_set_connection</literal> and
+          <literal>collation_connection</literal> so that it can return
+          month and weekday names containing non-ASCII characters.
+          Before 5.1.15, the return value is a binary string.
+        </para>
+
         <remark role="help-example"/>
 
 <programlisting>


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2007-01-24 19:21:36 UTC (rev 4629)
+++ trunk/refman-5.1/news-5.1.xml	2007-01-24 21:29:57 UTC (rev 4630)
Changed blocks: 2, Lines Added: 84, Lines Deleted: 0; 3428 bytes

@@ -153,6 +153,19 @@
 
       <listitem>
         <para>
+          <emphasis role="bold">Incompatible change</emphasis>:
+          Previously, the <literal>DATE_FORMAT()</literal> function
+          returned a binary string. Now it returns a string with a
+          character set and collation given by
+          <literal>character_set_connection</literal> and
+          <literal>collation_connection</literal> so that it can return
+          month and weekday names containing non-ASCII characters. (Bug
+          #22646)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Partitioning of tables using the <literal>FEDERATED</literal>
           storage engine is no longer permitted. Attempting to create
           such a table or to modify an existing table so that is uses

@@ -247,6 +260,77 @@
 
       <listitem>
         <para>
+          Using a view in combination with a <literal>USING</literal>
+          clause caused column aliases to be ignored. (Bug #25106)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Using <literal>ALTER TABLE</literal> to convert a
+          <literal>CSV</literal> table containing
+          <literal>NULL</literal> values to
<literal>MyISAM</literal>
+          resulted in warnings. (Bug #21328)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          A view was not handled correctly if the
+          <literal>SELECT</literal> part contained
+          &lsquo;<literal>\Z</literal>&rsquo;. (Bug #24293)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Inserting a row into a table without specifying a value for a
+          <literal>BINARY(<replaceable>N</replaceable>) NOT
+          NULL</literal> column caused the column to be set to spaces,
+          not zeroes. (Bug #14171)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          An assertion failed incorrectly for prepared statements that
+          contained a single-row non-correlated subquery that was used
+          as an argument of the IS NULL predicate. (Bug #25027)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          A table created with the <literal>ROW_FORMAT = FIXED</literal>
+          table option loses the option if an index is added or dropped
+          with <literal>CREATE INDEX</literal> or <literal>DROP
+          INDEX</literal>. (Bug #23404)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Dropping a user-defined function sometimes did not remove the
+          UDF entry from the <literal>mysql.proc</literal> table. (Bug
+          #15439)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          The <command>BUILD/check-cpu</command> script did not
+          recognize Celeron processors. (Bug #20061)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Some problems uncovered by Valgrind were fixed. (Bug #25396)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <command>mysql_fix_privilege_tables</command> did not handle a
           password containing embedded space or apostrophe characters.
           (Bug #17700)


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