Author: jstephens
Date: 2008-03-15 22:44:19 +0100 (Sat, 15 Mar 2008)
New Revision: 10264
Log:
Documented various Server bugfixes:
Bug #14637, Bug #25426, Bug #30081, Bug #34749
Modified:
trunk/dynamic-docs/changelog/mysqld-1.xml
Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml 2008-03-15 21:33:50 UTC (rev 10263)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml 2008-03-15 21:44:19 UTC (rev 10264)
Changed blocks: 1, Lines Added: 130, Lines Deleted: 0; 3533 bytes
@@ -6,9 +6,139 @@
]>
<changelog>
+ <logentry entrytype="bug">
+
+ <tags>
+ <manual type="NAME_CONST()"/>
+ <manual type="aggregate functions"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="34749"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.60"/>
+ <version ver="5.1.24"/>
+ <version ver="6.0.5"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Using <literal>NAME_CONST()</literal> with a negative number and
+ an aggregate function caused MySQL to crash. This could also
+ have a negative impact on replication.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <manual type="TIMESTAMP"/>
+ <manual type="ON UPDATE CURRENT_TIMESTAMP"/>
+ <manual type="ON_UPDATE_NOW_FLAG"/>
+ <manual type="get_schema_column_record()"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="30081"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.23"/>
+ <version ver="6.0.4"/>
+ </versions>
+
+ <message>
+
+ <para>
+ It was not possible for client applications to distinguish
+ between auto-set and auto-updated <literal>TIMESTAMP</literal>
+ column values.
+ </para>
+
+ <para>
+ To rectify this problem, a new
+ <literal>ON_UPDATE_NOW_FLAG</literal> flag is set by
+ Field_timestamp constructors whenever a column should be set to
+ <literal>NOW</literal> on <literal>UPDATE</literal>, and the
+ <literal>get_schema_column_record()</literal> function now
+ reports whether a timestamp column is set to
+ <literal>NOW</literal> on <literal>UPDATE</literal>. In
+ addition, such columns now display <literal>on update
+ CURRENT_TIMESTAMP</literal> in the <literal>Extra</literal>
+ column in the output from <literal>SHOW COLUMNS</literal>.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <manual type="DECIMAL"/>
+ <manual type="indexes"/>
+ <manual type="errors"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="25426"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.24"/>
+ <version ver="6.0.5"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Attempting to create an index with a prefix on a
+ <literal>DECIMAL</literal> column appeared to succeed with an
+ inaccurate warning message. Now, this action fails with the
+ error <errortext>Incorrect prefix key; the used key part isn't a
+ string, the used length is longer than the key part, or the
+ storage engine doesn't support unique prefix keys</errortext>.
+ </para>
+
+ </message>
+
+ </logentry>
+
<logentry entrytype="feature">
<tags>
+ <manual type="strings"/>
+ <manual type="performance"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="14637"/>
+ </bugs>
+
+ <versions>
+ <version ver="6.0.5"/>
+ </versions>
+
+ <message>
+
+ <para>
+ The performance of internal functions that trim multiple spaces
+ from strings when comparing them has been improved.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="feature">
+
+ <tags>
<highlight type="importantchange"/>
<manual type="INFORMATION_SCHEMA.PARAMETERS"/>
<manual type="ROUTINE_TYPE"/>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r10264 - trunk/dynamic-docs/changelog | jon | 15 Mar |
