Author: paul
Date: 2007-06-19 03:35:28 +0200 (Tue, 19 Jun 2007)
New Revision: 6855
Log:
r21857@frost: paul | 2007-06-18 20:15:13 -0500
Documented bugfixes:
Bug#26952
Bug#27643
Bug#28121
Bug#28427
Bug#28494
Bug#28505
Bug#28561
Bug#28571
Bug#28716
Modified:
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:26621
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:21856
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:18307
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:26621
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:21857
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:18307
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-06-19 01:35:05 UTC (rev 6854)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-06-19 01:35:28 UTC (rev 6855)
Changed blocks: 2, Lines Added: 80, Lines Deleted: 0; 3677 bytes
@@ -168,6 +168,76 @@
<listitem>
<para>
+ A query that grouped by the result of an expression returned a
+ different result when the expression was assigned to a user
+ variable. (Bug #28494)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The result of evaluation for a view's <literal>CHECK
+ OPTION</literal> option over an updated record and records of
+ merged tables was arbitrary and dependant on the order of
+ records in the merged tables during the execution of the
+ <literal>SELECT</literal> statement. (Bug #28716)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Outer join queries with <literal>ON</literal> conditions over
+ constant outer tables did not return
+ <literal>NULL</literal>-complemented rows when conditions were
+ evaluated to <literal>FALSE</literal>. (Bug #28571)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ An update on a multiple-table view with the CHECK OPTION
+ clause and a subquery in the WHERE condition could cause an
+ assertion failure. (Bug #28561)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>mysql_affected_rows()</literal> could return an
+ incorrect result for <literal>INSERT ... ON DUPLICATE KEY
+ UPDATE</literal> if the <literal>CLIENT_FOUND_ROWS</literal>
+ flag was set. (Bug #28505)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Storing a large number into a <literal>FLOAT</literal> or
+ <literal>DOUBLE</literal> column with a fixed length could
+ result in incorrect truncation of the number if the columns's
+ length was greater than 31. (Bug #28121)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>HASH</literal> indexes on <literal>VARCHAR</literal>
+ columns with binary collations did not ignore trailing spaces
+ from strings before comparisons. This could result in
+ duplicate records being successfully inserted into a
+ <literal>MEMORY</literal> table with unique key constraints. A
+ consequence was that internal <literal>MEMORY</literal> tables
+ used for <literal>GROUP BY</literal> calculation contained
+ duplicate rows that resulted in duplicate-key errors when
+ converting those temporary tables to
+ <literal>MyISAM</literal>, and that error was incorrectly
+ reported as a <literal>table is full</literal> error. (Bug
+ #27643)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Setting the <literal>key_cache_block_size</literal> system
variable to a value that is not a power of two resulted in
<literal>MyISAM</literal> table corruption. (Bug #28478)
@@ -1701,6 +1771,16 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ Added the <option>--service-startup-timeout</option> option
+ for <command>mysql.server</command> to specify how long to
+ wait for the server to start. If the server does not start
+ within the timeout period, <command>mysql.server</command>
+ exits with an error. (Bug #26952)
+ </para>
+ </listitem>
+
</itemizedlist>
<para>
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-06-19 01:35:05 UTC (rev 6854)
+++ trunk/refman-5.1/news-5.1.xml 2007-06-19 01:35:28 UTC (rev 6855)
Changed blocks: 2, Lines Added: 88, Lines Deleted: 0; 4046 bytes
@@ -270,6 +270,84 @@
<listitem>
<para>
+ A query that grouped by the result of an expression returned a
+ different result when the expression was assigned to a user
+ variable. (Bug #28494)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The result of evaluation for a view's <literal>CHECK
+ OPTION</literal> option over an updated record and records of
+ merged tables was arbitrary and dependant on the order of
+ records in the merged tables during the execution of the
+ <literal>SELECT</literal> statement. (Bug #28716)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Outer join queries with <literal>ON</literal> conditions over
+ constant outer tables did not return
+ <literal>NULL</literal>-complemented rows when conditions were
+ evaluated to <literal>FALSE</literal>. (Bug #28571)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ An update on a multiple-table view with the CHECK OPTION
+ clause and a subquery in the WHERE condition could cause an
+ assertion failure. (Bug #28561)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>mysql_affected_rows()</literal> could return an
+ incorrect result for <literal>INSERT ... ON DUPLICATE KEY
+ UPDATE</literal> if the <literal>CLIENT_FOUND_ROWS</literal>
+ flag was set. (Bug #28505)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using <literal>ALTER TABLE</literal> to move columns resulted
+ only in the columns being renamed. The table contents were not
+ changed. (Bug #28427)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Storing a large number into a <literal>FLOAT</literal> or
+ <literal>DOUBLE</literal> column with a fixed length could
+ result in incorrect truncation of the number if the columns's
+ length was greater than 31. (Bug #28121)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>HASH</literal> indexes on <literal>VARCHAR</literal>
+ columns with binary collations did not ignore trailing spaces
+ from strings before comparisons. This could result in
+ duplicate records being successfully inserted into a
+ <literal>MEMORY</literal> table with unique key constraints. A
+ consequence was that internal <literal>MEMORY</literal> tables
+ used for <literal>GROUP BY</literal> calculation contained
+ duplicate rows that resulted in duplicate-key errors when
+ converting those temporary tables to
+ <literal>MyISAM</literal>, and that error was incorrectly
+ reported as a <literal>table is full</literal> error. (Bug
+ #27643)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Setting the <literal>key_cache_block_size</literal> system
variable to a value that is not a power of two resulted in
<literal>MyISAM</literal> table corruption. (Bug #28478)
@@ -4316,6 +4394,16 @@
<listitem>
<para>
+ Added the <option>--service-startup-timeout</option> option
+ for <command>mysql.server</command> to specify how long to
+ wait for the server to start. If the server does not start
+ within the timeout period, <command>mysql.server</command>
+ exits with an error. (Bug #26952)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Added the <literal>innodb_stats_on_metadata</literal> system
variable to enable control over whether
<literal>InnoDB</literal> performs statistics gathering when
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r6855 - in trunk: . refman-5.0 refman-5.1 | paul | 19 Jun |
