List:Commits« Previous MessageNext Message »
From:paul Date:January 24 2007 12:53am
Subject:svn commit - mysqldoc@docsrva: r4616 - in trunk: . refman-4.1 refman-5.0 refman-5.1
View as plain text  
Author: paul
Date: 2007-01-24 01:53:25 +0100 (Wed, 24 Jan 2007)
New Revision: 4616

Log:
 r18737@polar:  paul | 2007-01-23 18:52:46 -0600
 Documented bugfixes:
 Bug#17700
 Bug#21809
 Bug#24299
 
 Merged relevant ES bugfixes into CS release notes.


Modified:
   trunk/refman-4.1/news-4.1.xml
   trunk/refman-5.0/releasenotes-cs-5.0.xml
   trunk/refman-5.0/releasenotes-es-5.0.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:18735
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:15213
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:18737
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:15213
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/news-4.1.xml
===================================================================
--- trunk/refman-4.1/news-4.1.xml	2007-01-24 00:21:29 UTC (rev 4615)
+++ trunk/refman-4.1/news-4.1.xml	2007-01-24 00:53:25 UTC (rev 4616)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 0; 736 bytes

@@ -211,6 +211,14 @@
 
       <listitem>
         <para>
+          <command>mysql_fix_privilege_tables</command> did not handle a
+          password containing embedded space or apostrophe characters.
+          (Bug #17700)
+        </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


Modified: trunk/refman-5.0/releasenotes-cs-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-cs-5.0.xml	2007-01-24 00:21:29 UTC (rev 4615)
+++ trunk/refman-5.0/releasenotes-cs-5.0.xml	2007-01-24 00:53:25 UTC (rev 4616)
Changed blocks: 3, Lines Added: 50, Lines Deleted: 0; 2580 bytes

@@ -52,6 +52,16 @@
 
       <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>
+          global status variable (viewable with the <literal>SHOW GLOBAL
+          STATUS</literal> statement). (Bug #23159)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <literal>NDB Cluster</literal>: Setting the configuration
           parameter <literal>LockPagesInMainMemory</literal> had no
           effect. (Bug #24461)

@@ -341,6 +351,37 @@
 
       <listitem>
         <para>
+          <command>mysql_fix_privilege_tables</command> did not handle a
+          password containing embedded space or apostrophe characters.
+          (Bug #17700)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Foreign key identifiers for <literal>InnoDB</literal> tables
+          could not contain certain characters. (Bug #24299)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          In some cases, the parser failed to distinguish a user-defined
+          function from a stored function. (Bug #21809)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          With <literal>innodb_file_per_table</literal> enabled,
+          <literal>InnoDB</literal> displayed incorrect file times in
+          the output from <literal>SHOW TABLE STATUS</literal>. (Bug
+          #24712)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           The stack size for NetWare binaries was increased to 128KB to
           prevent problems caused by insufficient stack size. (Bug
           #23504)

@@ -1219,6 +1260,15 @@
 
       <listitem>
         <para>
+          If an <literal>init_connect</literal> SQL statement produced
+          an error, the connection was silently terminated with no error
+          message. Now the server writes a warning to the error log.
+          (Bug #22158)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           The internal SQL interpreter of <literal>InnoDB</literal>
           placed an unnecessary lock on the supremum record when
           <literal>innodb_locks_unsafe_for_binlog=1</literal>. This


Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml	2007-01-24 00:21:29 UTC (rev 4615)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml	2007-01-24 00:53:25 UTC (rev 4616)
Changed blocks: 2, Lines Added: 31, Lines Deleted: 0; 1720 bytes

@@ -601,6 +601,28 @@
 
       <listitem>
         <para>
+          <command>mysql_fix_privilege_tables</command> did not handle a
+          password containing embedded space or apostrophe characters.
+          (Bug #17700)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Foreign key identifiers for <literal>InnoDB</literal> tables
+          could not contain certain characters. (Bug #24299)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          In some cases, the parser failed to distinguish a user-defined
+          function from a stored function. (Bug #21809)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           With <literal>innodb_file_per_table</literal> enabled,
           <literal>InnoDB</literal> displayed incorrect file times in
           the output from <literal>SHOW TABLE STATUS</literal>. (Bug

@@ -1748,6 +1770,15 @@
 
       <listitem>
         <para>
+          If an <literal>init_connect</literal> SQL statement produced
+          an error, the connection was silently terminated with no error
+          message. Now the server writes a warning to the error log.
+          (Bug #22158)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           The internal SQL interpreter of <literal>InnoDB</literal>
           placed an unnecessary lock on the supremum record when
           <literal>innodb_locks_unsafe_for_binlog=1</literal>. This


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2007-01-24 00:21:29 UTC (rev 4615)
+++ trunk/refman-5.1/news-5.1.xml	2007-01-24 00:53:25 UTC (rev 4616)
Changed blocks: 3, Lines Added: 31, Lines Deleted: 0; 1873 bytes

@@ -247,6 +247,21 @@
 
       <listitem>
         <para>
+          <command>mysql_fix_privilege_tables</command> did not handle a
+          password containing embedded space or apostrophe characters.
+          (Bug #17700)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Foreign key identifiers for <literal>InnoDB</literal> tables
+          could not contain certain characters. (Bug #24299)
+        </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)

@@ -1621,6 +1636,13 @@
 
       <listitem>
         <para>
+          In some cases, the parser failed to distinguish a user-defined
+          function from a stored function. (Bug #21809)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           In some cases, a function that should be parsed as a
           user-defined function was parsed as a stored function. (Bug
           #24736)

@@ -2118,6 +2140,15 @@
 
       <listitem>
         <para>
+          If an <literal>init_connect</literal> SQL statement produced
+          an error, the connection was silently terminated with no error
+          message. Now the server writes a warning to the error log.
+          (Bug #22158)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           If a table contains an <literal>AUTO_INCREMENT</literal>
           column, inserting into an insertable view on the table that
           does not include the <literal>AUTO_INCREMENT</literal> column


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