Author: jstephens
Date: 2008-07-28 08:11:16 +0200 (Mon, 28 Jul 2008)
New Revision: 11392
Log:
More work on WL#4169 (patch #5)
Modified:
trunk/dynamic-docs/changelog/mysqld.xml
Modified: trunk/dynamic-docs/changelog/mysqld.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld.xml 2008-07-28 00:28:30 UTC (rev 11391)
+++ trunk/dynamic-docs/changelog/mysqld.xml 2008-07-28 06:11:16 UTC (rev 11392)
Changed blocks: 33, Lines Added: 80, Lines Deleted: 78; 12560 bytes
@@ -29125,6 +29125,8 @@
</logentry>
+<!-- WL#4169 EDITS THROUGH HERE -->
+
<logentry entrytype="bug">
<bugs>
@@ -29138,9 +29140,9 @@
<message>
<para>
- Fixed conversion of floating-point values to character fields
- when the absolute value of the float was less than 1, and also
- fixed calculation of length for negative values.
+ Conversion of floating-point values to character values was not
+ performed correctly when the absolute value of the float was
+ less than 1 (including negative values).
</para>
</message>
@@ -30209,9 +30211,9 @@
<message>
<para>
- Fixed a bug that caused the MySQL server to crash when
- attempting to execute a prepared statement with <literal>SELECT
- ... INTO @var</literal> for a second time.
+ The MySQL server crashed when attempting to execute a prepared
+ statement with <literal>SELECT ... INTO @var</literal> for the
+ second time.
</para>
</message>
@@ -30232,8 +30234,8 @@
<message>
<para>
- Fixed an optimizer bug in computing the union of two ranges for
- the <literal>OR</literal> operator.
+ The optimizer did not compute the union of two ranges for the
+ <literal>OR</literal> operator correctly.
</para>
</message>
@@ -31332,8 +31334,8 @@
<message>
<para>
- Fixed a rare race condition which could lead to <literal>FLUSH
- TABLES WITH READ LOCK</literal> hanging.
+ A rare race condition could cause <literal>FLUSH TABLES WITH
+ READ LOCK</literal> to hang.
</para>
</message>
@@ -31679,9 +31681,11 @@
<message>
<para>
- Fixed a problem resulting from setting the
+ On Linux platforms, setting the
<literal>character_set_results</literal> variable to
- <literal>NULL</literal>.
+ <literal>NULL</literal> and then attempting to retrieve it using
+ <literal>SELECT @@character_set_results</literal> caused the
+ server to crash.
</para>
</message>
@@ -31928,9 +31932,9 @@
<message>
<para>
- Fixed illegal internal field length of user variables of integer
- type. This showed up when creating a table as <literal>SELECT
- @<replaceable>var_name</replaceable></literal>.
+ The internal field length of integer user variables was
+ incorrect. This showed up when creating a table as
+ <literal>SELECT @<replaceable>var_name</replaceable></literal>.
</para>
</message>
@@ -32445,8 +32449,8 @@
<message>
<para>
- Fixed a data loss bug in <literal>REPAIR TABLE ...
- USE_FRM</literal> when used with tables that contained
+ <literal>REPAIR TABLE ... USE_FRM</literal> could cause data
+ loss when used with tables that contained
<literal>TIMESTAMP</literal> columns and were created in 4.0.x.
</para>
@@ -32853,9 +32857,9 @@
<message>
<para>
- Fixed a <command>mysqldump</command> crash that occurred with
- the <option>--complete-insert</option> option when dumping
- tables with a large number of long column names.
+ <command>mysqldump</command> crashed using the
+ <option>--complete-insert</option> option while dumping tables
+ with a large number of long column names.
</para>
</message>
@@ -33180,8 +33184,8 @@
<message>
<para>
- Fixed a crash when the replication slave was unable to create
- the first relay log.
+ If a replication slave was unable to create the first relay log,
+ it crashed.
</para>
</message>
@@ -33716,7 +33720,7 @@
<message>
<para>
- Fixed bug in prepared statements with <literal>OUTER
+ Prepared statements did not work correctly with <literal>OUTER
JOIN</literal>.
</para>
@@ -33940,7 +33944,8 @@
<message>
<para>
- Fixed output of <command>mysqldump --tab</command>.
+ The output of <command>mysqldump --tab</command> was not
+ correct.
</para>
</message>
@@ -34039,7 +34044,8 @@
<message>
<para>
- Fixed compile error when using GCC4 on AMD64.
+ The server did not compile correctly when using
+ <command>gcc4</command> on AMD64 platforms.
</para>
</message>
@@ -34204,9 +34210,9 @@
<message>
<para>
- Fixed a server crash resulting from use of
- <function role="sql">AVG(DISTINCT)</function> with
- <literal>GROUP BY ... WITH ROLLUP</literal>.
+ Using <function role="sql">AVG(DISTINCT)</function> with
+ <literal>GROUP BY ... WITH ROLLUP</literal> caused the server to
+ crash.
</para>
</message>
@@ -34249,9 +34255,8 @@
<message>
<para>
- Fixed a bug in <literal>libmysqlclient</literal> with wrong
- conversion of zero date values (<literal>0000-00-00</literal>)
- to strings.
+ <literal>libmysqlclient</literal> did not convert zero date
+ values (<literal>0000-00-00</literal>) to strings correctly.
</para>
</message>
@@ -34460,8 +34465,9 @@
<message>
<para>
- Fixed server crash when left expression of
- <literal>IN/ALL/ANY</literal> comparison was a subquery.
+ Using a compariosn where the left expression of
+ <literal>IN</literal>, <literal>ALL</literal>, or
+ <literal>ANY</literal> was a subquery caused the server to crash
</para>
</message>
@@ -34574,9 +34580,9 @@
<message>
<para>
- Fixed that in some replication error messages, a very long query
- caused the rest of the message to be invisible (truncated), by
- putting the query last in the message.
+ In some replication error messages, a very long query caused the
+ rest of the message to be invisible (truncated), by putting the
+ query last in the message.
</para>
</message>
@@ -35102,7 +35108,7 @@
<message>
<para>
- Prepared statements with all types of subqueries fixed.
+ Prepared statements now work with all types of subqueries.
</para>
</message>
@@ -35126,8 +35132,8 @@
<message>
<para>
- Fixed a server crash resulting from <literal>GROUP BY</literal>
- on a decimal expression.
+ Using <literal>GROUP BY</literal> on a decimal expression caused
+ the server to crash.
</para>
</message>
@@ -35758,9 +35764,9 @@
<message>
<para>
- Fixed a server crash for <literal>INSERT ... ON DUPLICATE KEY
- UPDATE</literal> with <literal>MERGE</literal> tables, which do
- not have unique indexes.
+ <literal>INSERT ... ON DUPLICATE KEY UPDATE</literal> with
+ <literal>MERGE</literal> tables, which do not have unique
+ indexes, caused the server to crash.
</para>
</message>
@@ -35877,10 +35883,10 @@
<message>
<para>
- Fixed problem where running
- <command>mysql_fix_privilege_tables</command> could result in
- grant table columns with too-short lengths if the server
- character set had been set to a multi-byte character set first.
+ Running <command>mysql_fix_privilege_tables</command> could
+ result in grant table columns with lengths that were too short
+ if the server character set had been set to a multi-byte
+ character set first.
</para>
</message>
@@ -36194,9 +36200,9 @@
<message>
<para>
- Fixed a bug which caused the server to crash when the deprecated
- <literal>libmysqlclient</literal> function
- <function role="capi">mysql_create_db()</function> was called.
+ Invoking the deprecated <literal>libmysqlclient</literal>
+ function <function role="capi">mysql_create_db()</function>
+ caused the server to crash.
</para>
</message>
@@ -36269,10 +36275,9 @@
<message>
<para>
- Fixed a bug in the server when after reaching a certain limit of
- prepared statements per connection (97), statement ids began to
- overlap, so occasionally wrong statements were chosen for
- execution.
+ After reaching a certain limit of prepared statements per
+ connection (97), statement IDs began to overlap, so occasionally
+ wrong statements were chosen for execution.
</para>
</message>
@@ -36732,9 +36737,9 @@
</programlisting>
<para>
- This bugfix enables alias declarations to be declared only in
- the <replaceable>table_references</replaceable> part. Elsewhere
- in the statement, alias references are allowed but not alias
+ This fix enables alias declarations to be made only in the
+ <replaceable>table_references</replaceable> part. Elsewhere in
+ the statement, alias references are allowed but not alias
declarations. However, this patch was reverted in MySQL 5.0.54
because it changed the behavior of a General Availability MySQL
release.
@@ -37018,7 +37023,7 @@
<message>
<para>
- Incorporated some portability fixes into the definition of
+ Incorporated portability fixes into the definition of
<literal>__attribute__</literal> in
<filename>my_global.h</filename>.
</para>
@@ -37045,10 +37050,10 @@
<message>
<para>
- Fixed a bug that could cause <literal>MyISAM</literal> index
- corruption when key values start with character codes below
+ <literal>MyISAM</literal> indexes could be corrupted when key
+ values started with character codes below
<literal>BLANK</literal>. This was caused by the new key sort
- order in 4.1.
+ order instroduced in MySQL 4.1.
</para>
</message>
@@ -37238,9 +37243,8 @@
<message>
<para>
- Fixed a server crash resulting from use of <literal>DISTINCT
- AVG()</literal> with <literal>GROUP BY ... WITH
- ROLLUP</literal>.
+ Usi <literal>DISTINCT AVG()</literal> with <literal>GROUP BY ...
+ WITH ROLLUP</literal> caused the server to crash.
</para>
</message>
@@ -37698,9 +37702,9 @@
<message>
<para>
- Fixed wrong <literal>UNION</literal> results if display length
- of fields for numeric types was set less than real length of
- values in them.
+ <literal>UNION</literal> returned incorrect results if the
+ display length of columns for numeric types was set to less than
+ the actual length of values in them.
</para>
</message>
@@ -38324,7 +38328,7 @@
<message>
<para>
- Some problems uncovered by Valgrind were fixed.
+ A number of issues were uncovered by Valgrind.
</para>
</message>
@@ -38397,9 +38401,9 @@
<message>
<para>
- Fixed incorrect referencing to column by name from subquery to
- outer query in case of using temporary table by outer query and
- placing subquery in the <literal>WHERE</literal> clause.
+ A reference to a column by name from a <literal>WHERE</literal>
+ subquery to an outer query, with use of a temporary table by the
+ outer query.
</para>
</message>
@@ -39144,10 +39148,10 @@
<para>
The <option>--collation-server</option> server option was being
- ignored. With the fix for this problem, if you choose a
- non-default character set with
- <option>--character-set-server</option>, you should also use
- <option>--collation-server</option> to specify the collation.
+ ignored. With the fix, if you choose a non-default character set
+ with <option>--character-set-server</option>, you should also
+ use <option>--collation-server</option> to specify the
+ collation.
</para>
</message>
@@ -39748,8 +39752,8 @@
<message>
<para>
- Fixed <literal>SELECT .. LIMIT 0</literal> to return proper row
- count for <literal>SQL_CALC_FOUND_ROWS</literal>.
+ <literal>SELECT .. LIMIT 0</literal> did not return the proper
+ row count for <literal>SQL_CALC_FOUND_ROWS</literal>.
</para>
</message>
@@ -39860,8 +39864,6 @@
</logentry>
-<!-- WL#4169 EDITS THROUGH HERE -->
-
<logentry entrytype="bug">
<tags>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r11392 - trunk/dynamic-docs/changelog | jon | 28 Jul |
