Author: jstephens
Date: 2006-07-04 14:05:58 +0200 (Tue, 04 Jul 2006)
New Revision: 2617
Log:
Documenting Server bugfixes:
Bug #14896, Bug #16168, Bug #16377, Bug #18462
Documenting fix for Partitioning Bug #20086
Partitioning Limitations: non-Cluster tables that are partitioned by KEY
should be dumped/reloaded when upgrading (Thanks, Bar!)
Modified:
trunk/refman-5.1/partitioning.xml
trunk/refman-common/news-4.1.xml
trunk/refman-common/news-5.0.xml
trunk/refman-common/news-5.1.xml
Modified: trunk/refman-5.1/partitioning.xml
===================================================================
--- trunk/refman-5.1/partitioning.xml 2006-07-04 06:06:43 UTC (rev 2616)
+++ trunk/refman-5.1/partitioning.xml 2006-07-04 12:05:58 UTC (rev 2617)
@@ -3947,6 +3947,14 @@
storage engine.
</para>
</listitem>
+
+ <listitem>
+ <para>
+ When performing an upgrade, any non-Cluster tables that are
+ partitioned by <literal>KEY</literal> must be dumped and
+ reloaded.
+ </para>
+ </listitem>
<listitem>
<para>
Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml 2006-07-04 06:06:43 UTC (rev 2616)
+++ trunk/refman-common/news-4.1.xml 2006-07-04 12:05:58 UTC (rev 2617)
@@ -211,6 +211,36 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ The omission of leading zeroes in dates could lead to
+ erroneous results when these were compared with the output of
+ certain date and time functions. (Bug #16377)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Certain queries having a <literal>WHERE</literal> clause that
+ included conditions on multi-part keys with more than 2 key
+ parts could produce incorrect results and send
+ <errortext>[Note] Use_count: Wrong count for key
+ at...</errortext> messages to <literal>STDERR</literal>.
+ (Bug #16168)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ An invalid comparison between keys in partial indexes over
+ multi-byte character fields could lead to incorrect result
+ sets if the selected query execution plan used a range scan by
+ a partial index over a <literal>UTF8</literal> character
+ field. This also caused incorrect results under similar
+ circumstances with many other character sets. (Bug #14896)
+ </para>
+ </listitem>
<listitem>
<para>
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2006-07-04 06:06:43 UTC (rev 2616)
+++ trunk/refman-common/news-5.0.xml 2006-07-04 12:05:58 UTC (rev 2617)
@@ -208,6 +208,17 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ Certain queries having a <literal>WHERE</literal> clause that
+ included conditions on multi-part keys with more than 2 key
+ parts could produce incorrect results and send
+ <errortext>[Note] Use_count: Wrong count for key
+ at...</errortext> messages to <literal>STDERR</literal>.
+ (Bug #16168)
+ </para>
+ </listitem>
<listitem>
<para>
@@ -417,6 +428,32 @@
<listitem>
<para>
+ <command>mysqldump</command> produced garbled output for view
+ definitions. (Bug #)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The omission of leading zeroes in dates could lead to
+ erroneous results when these were compared with the output of
+ certain date and time functions. (Bug #16377)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ An invalid comparison between keys in partial indexes over
+ multi-byte character fields could lead to incorrect result
+ sets if the selected query execution plan used a range scan by
+ a partial index over a <literal>UTF8</literal> character
+ field. This also caused incorrect results under similar
+ circumstances with many other character sets. (Bug #14896)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>NDB Cluster</literal>: Cluster system status
variables were not updated. (Bug #11459)
</para>
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-07-04 06:06:43 UTC (rev 2616)
+++ trunk/refman-common/news-5.1.xml 2006-07-04 12:05:58 UTC (rev 2617)
@@ -298,6 +298,34 @@
<listitem>
<para>
+ Queries on tables that were partitioned by
+ <literal>KEY</literal> and had a <literal>VARCHAR</literal>
+ column as the partitioning key produced an empty result set.
+ (Bug #20086)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The omission of leading zeroes in dates could lead to
+ erroneous results when these were compared with the output of
+ certain date and time functions. (Bug #16377)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ An invalid comparison between keys in partial indexes over
+ multi-byte character fields could lead to incorrect result
+ sets if the selected query execution plan used a range scan by
+ a partial index over a <literal>UTF8</literal> character
+ field. This also caused incorrect results under similar
+ circumstances with many other character sets. (Bug #14896)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
A prepared statement that altered partitioned table within a
stored procedure failed with the error <errortext>Unknown
prepared statement handler</errortext>. (Bug #17138)
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r2617 - in trunk: refman-5.1 refman-common | jon | 4 Jul |
