Author: paul
Date: 2007-01-23 22:03:43 +0100 (Tue, 23 Jan 2007)
New Revision: 4613
Log:
r18727@polar: paul | 2007-01-23 15:02:43 -0600
Document bugfixes:
Bug#14094
Bug#17635
Bug#19725
Bug#20390
Bug#20396
Bug#22119
Bug#22645
Bug#24660
Bug#24712
Bug#25026
Modified:
trunk/refman-4.1/news-4.1.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:18717
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:18727
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-23 19:52:38 UTC (rev 4612)
+++ trunk/refman-4.1/news-4.1.xml 2007-01-23 21:03:43 UTC (rev 4613)
Changed blocks: 1, Lines Added: 24, Lines Deleted: 0; 1225 bytes
@@ -201,6 +201,30 @@
<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
+ <literal>MyISAM</literal> tables as corrupt. (Bug #22119)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>SET lc_time_names =
+ <replaceable>value</replaceable></literal> allowed only exact
+ literal values, not expression values. (Bug #22647)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Changes to the <literal>lc_time_names</literal> system
+ variable were not replicated. (Bug #22645)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<command>mysqldump --order-by-primary</command> failed if the
primary key name was an identifier that required quoting. (Bug
#13926)
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-01-23 19:52:38 UTC (rev 4612)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-01-23 21:03:43 UTC (rev 4613)
Changed blocks: 3, Lines Added: 67, Lines Deleted: 0; 3164 bytes
@@ -78,6 +78,55 @@
<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)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A stored routine containing semicolon in its body could not be
+ reloaded from a dump of a binary log. (Bug #20396)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For <literal>SET</literal>, <literal>SELECT</literal>, and
+ <literal>DO</literal> statements that invoked a stored
+ function from a database other than the default database, the
+ function invocation could fail to be replicated. (Bug #19725)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>SET lc_time_names =
+ <replaceable>value</replaceable></literal> allowed only exact
+ literal values, not expression values. (Bug #22647)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Changes to the <literal>lc_time_names</literal> system
+ variable were not replicated. (Bug #22645)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>SELECT ... FOR UPDATE</literal>, <literal>SELECT ...
+ LOCK IN SHARE MODE</literal>, <literal>DELETE</literal>, and
+ <literal>UPDATE</literal> statements executed using a full
+ table scan were not releasing locks on rows that did not
+ satisfy the <literal>WHERE</literal> condition. (Bug #20390)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
A stored procedure, executed from a connection using a binary
character set, and which wrote multibyte data, would write
incorrectly escaped entries to the binary log. This caused
@@ -167,6 +216,15 @@
<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
+ <literal>MyISAM</literal> tables as corrupt. (Bug #22119)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Instance Manager could crash during shutdown. (Bug #19044)
</para>
</listitem>
@@ -533,6 +591,15 @@
<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)
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-01-23 19:52:38 UTC (rev 4612)
+++ trunk/refman-5.1/news-5.1.xml 2007-01-23 21:03:43 UTC (rev 4613)
Changed blocks: 1, Lines Added: 85, Lines Deleted: 0; 3528 bytes
@@ -247,6 +247,91 @@
<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)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ In the <literal>INFORMATION_SCHEMA.KEY_COLUMN_USAGE</literal>
+ table, the value displayed for the
+ <literal>REFERENCED_TABLE_NAME</literal> column was the table
+ name as encoded for disk storage, not the actual table name.
+ (Bug #25026)
+ </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
+ <literal>MyISAM</literal> tables as corrupt. (Bug #22119)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A stored routine containing semicolon in its body could not be
+ reloaded from a dump of a binary log. (Bug #20396)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For <literal>SET</literal>, <literal>SELECT</literal>, and
+ <literal>DO</literal> statements that invoked a stored
+ function from a database other than the default database, the
+ function invocation could fail to be replicated. (Bug #19725)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For <literal>ENUM</literal> columns defined such that
+ enumeration values contained commas, the commas were mapped to
+ <literal>0xff</literal>. (Bug #24660)
+ </para>
+
+ <para>
+ <emphasis role="bold">Upgrade note</emphasis>: The fix for
+ this problem affects tables containing <literal>ENUM</literal>
+ columns that actually do have <literal>0xff</literal> in
+ enumeration values. Such tables should be dumped using
+ <command>mysqldump</command> with the current server before
+ upgrading to MySQL 5.1.15 or higher and reloading the tables.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>SET lc_time_names =
+ <replaceable>value</replaceable></literal> allowed only exact
+ literal values, not expression values. (Bug #22647)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Changes to the <literal>lc_time_names</literal> system
+ variable were not replicated. (Bug #22645)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>SELECT ... FOR UPDATE</literal>, <literal>SELECT ...
+ LOCK IN SHARE MODE</literal>, <literal>DELETE</literal>, and
+ <literal>UPDATE</literal> statements executed using a full
+ table scan were not releasing locks on rows that did not
+ satisfy the <literal>WHERE</literal> condition. (Bug #20390)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
A stored procedure, executed from a connection using a binary
character set, and which wrote multibyte data, would write
incorrectly escaped entries to the binary log. This caused
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r4613 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 23 Jan |
