Author: jstephens
Date: 2007-12-14 19:10:21 +0100 (Fri, 14 Dec 2007)
New Revision: 9322
Log:
Documented a few misc. Server bugfixes:
Bug #19723, Bug #24907, Bug #26788, Bug #27545, Bug #30453
Modified:
trunk/dynamic-docs/changelog/mysqld-1.xml
Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml 2007-12-14 17:35:30 UTC (rev 9321)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml 2007-12-14 18:10:21 UTC (rev 9322)
Changed blocks: 1, Lines Added: 255, Lines Deleted: 3; 6277 bytes
@@ -5,31 +5,283 @@
%all.entities;
]>
<changelog>
-
+
<logentry entrytype="bug">
+
<tags>
+ <manual type="data types"/>
+ <manual type="cast"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="30453"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.54"/>
+ <version ver="5.1.23"/>
+ <version ver="6.0.5"/>
+ </versions>
+
+ <message>
+
+ <para>
+ When casting a string value to an integer, cases where the input
+ string contained a decimal point and was long enough to overrun
+ the <literal>unsigned long long</literal> type were not handled
+ correctly. The position of the decimal point was not taken into
+ account which resulted in miscalculated numbers and incorrect
+ truncation to appropriate SQL data type limits.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <manual type="NAME_CONST()"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="27545"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.54"/>
+ <version ver="5.1.23"/>
+ <version ver="6.0.5"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Some queries using the
+ <function role="sql">NAME_CONST()</function> function failed to
+ return either a result or an error to the client, causing it to
+ hang. This was due to the fact that there was no check to insure
+ that both arguments to this function were constant expressions.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <manual type="precision"/>
+ <manual type="FLOAT"/>
+ <manual type="CHAR"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="26788"/>
+ <seealsobug bugid="12860"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.54"/>
+ <version ver="5.1.23"/>
+ <version ver="6.0.5"/>
+ </versions>
+
+ <message>
+
+ <para>
+ <command>mysqld</command> sometimes miscalculated the number of
+ digits required when storing a floating-point number in a
+ <literal>CHAR</literal> column. This caused the value to be
+ truncated, or (when using a debug build) caused the server to
+ crash.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <manual type="arithmetic precision"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="24907"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.54"/>
+ <version ver="5.1.23"/>
+ <version ver="6.0.5"/>
+ </versions>
+
+ <message>
+
+ <para>
+ If the expected precision of an arithmetic expression exceeded
+ the maximum precision supported by MySQL, the precision of the
+ result was reduced by an unpredictable or arbitrary amount,
+ rather than to the maximum precision. In some cases, exceeding
+ the maximum supported precision could also lead to a crash of
+ the server.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <manual type="KILL"/>
+ <manual type="Mac OS X"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="19723"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.23"/>
+ <version ver="6.0.5"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Issuing an SQL <literal>KILL</literal> of the active connection
+ caused an error on Mac OS X.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
<highlight type="partitioning"/>
+ <manual type="ORDER BY DESC"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="31890"/>
+ <seealsobug bugid="31001"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.23"/>
+ <version ver="6.0.5"/>
+ </versions>
+
+ <message>
+
+ <para>
+ <literal>ORDER BY ... DESC</literal> did not always work
+ correctly when selecting from partitioned tables.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="partitioning"/>
+ <manual type="AUTO_INCREMENT"/>
+ <manual type="InnoDB"/>
+ <manual type="ARCHIVE"/>
+ <manual type="SHOW CREATE TABLE"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="32247"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.23"/>
+ <version ver="6.0.5"/>
+ </versions>
+
+ <message>
+
+ <para>
+ <literal>SHOW CREATE TABLE</literal> misreported the value of
+ <literal>AUTO_INCREMENT</literal> for partitioned tables using
+ either of the <literal>InnoDB</literal> or
+ <literal>ARCHIVE</literal> storage engines.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="partitioning"/>
+ <manual type="SET"/>
+ <manual type="GROUP BY"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="32772"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.23"/>
+ <version ver="6.0.5"/>
+ </versions>
+
+ <message>
+
+ <para>
+ A query of the form <literal>SELECT
+ <replaceable>col1</replaceable> FROM
+ <replaceable>table</replaceable> GROUP BY (SELECT
+ <replaceable>col2</replaceable> FROM
+ <replaceable>table</replaceable> LIMIT 1);</literal> against a
+ partitioned <replaceable>table</replaceable> having a
+ <literal>SET</literal> column crashed the server.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="partitioning"/>
<manual type="INFORMATION_SCHEMA"/>
<manual type="ALTER TABLE"/>
</tags>
+
<bugs>
<fixes bugid="32178"/>
</bugs>
+
<versions>
<version ver="5.1.23"/>
<version ver="6.0.5"/>
</versions>
+
<message>
+
<para>
Selecting from <literal>INFORMATION_SCHEMA.PARTITIONS</literal>
while partition management statements (for example,
<literal>ALTER TABLE ... ADD PARTITION</literal>) were executing
caused the server to crash.
</para>
+
</message>
+
</logentry>
-
-
+
<logentry entrytype="feature">
<tags>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r9322 - trunk/dynamic-docs/changelog | jon | 14 Dec |
