Author: jstephens
Date: 2006-03-04 10:28:38 +0100 (Sat, 04 Mar 2006)
New Revision: 1513
Log:
Documenting 5.0 bugfixes:
Bug #13134, Bug #14169, Bug #17602, Bug #17615, Bug #17826
Modified:
trunk/refman-5.0/functions.xml
trunk/refman-5.1/functions.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.0/functions.xml
===================================================================
--- trunk/refman-5.0/functions.xml 2006-03-04 04:11:22 UTC (rev 1512)
+++ trunk/refman-5.0/functions.xml 2006-03-04 09:28:38 UTC (rev 1513)
@@ -14422,6 +14422,18 @@
If a maximum length has been set, the result is truncated to
this maximum length.
</para>
+
+ <para>
+ Beginning with MySQL 5.0.19, the type returned by
+ <literal>GROUP_CONCAT()</literal> is always
+ <literal>VARCHAR</literal> unless
+ <literal>group_concat_max_len</literal> is greater than 512,
+ in which case, it returns a <literal>BLOB</literal>.
+ (Previously, it returned a <literal>BLOB</literal> with
+ <literal>group_concat_max_len</literal> greater than 512
+ only if the query included an <literal>ORDER BY</literal>
+ clause.)
+ </para>
<remark role="note">
Commented out until someone can say what GROUP_CONCAT() can
Modified: trunk/refman-5.1/functions.xml
===================================================================
--- trunk/refman-5.1/functions.xml 2006-03-04 04:11:22 UTC (rev 1512)
+++ trunk/refman-5.1/functions.xml 2006-03-04 09:28:38 UTC (rev 1513)
@@ -14848,6 +14848,13 @@
If a maximum length has been set, the result is truncated to
this maximum length.
</para>
+
+ <para>
+ The type returned by <literal>GROUP_CONCAT()</literal> is
+ always <literal>VARCHAR</literal> unless
+ <literal>group_concat_max_len</literal> is greater than 512,
+ in which case, it returns a <literal>BLOB</literal>.
+ </para>
<remark role="note">
Commented out until someone can say what GROUP_CONCAT() can
Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml 2006-03-04 04:11:22 UTC (rev 1512)
+++ trunk/refman-common/news-4.1.xml 2006-03-04 09:28:38 UTC (rev 1513)
@@ -382,6 +382,16 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ The length of a <literal>VARCHAR()</literal> column that used
+ the <literal>utf8</literal> character set would increase each
+ time the table was re-created in a stored procedure or
+ prepared statement, eventually causing the <literal>CREATE
+ TABLE</literal> statement to fail. (Bug #13134)
+ </para>
+ </listitem>
<listitem>
<para>
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2006-03-04 04:11:22 UTC (rev 1512)
+++ trunk/refman-common/news-5.0.xml 2006-03-04 09:28:38 UTC (rev 1513)
@@ -166,7 +166,53 @@
For a full list of changes, please refer to the changelog sections
for each individual 5.0.x release.
</para>
+
+ <section id="news-5-0-20">
+ <title>&title-news-5-0-20;</title>
+ <remark role="todo">
+ [js] Uncomment when there are feature changes to document.
+ </remark>
+
+ <!--
+
+ <para>
+ Functionality added or changed:
+ </para>
+
+ <remark role="note">
+ [js] Please leave items marked Incompatible Change at the top of
+ the listing.
+ </remark>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+
+ </para>
+ </listitem>
+ </itemizedlist>
+ -->
+
+ <para>
+ Bugs fixed:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ Updating the value of a Unicode <literal>VARCHAR</literal>
+ column with the result returned by a stored function would
+ cause the insertion of ASCII characters into the column
+ instead of Unicode, even where the function's return type was
+ also declared as Unicode. (Bug #17615)
+ </para>
+ </listitem>
+ </itemizedlist>
+
+
+ </section>
+
<section id="news-5-0-19">
<title>&title-news-5-0-19;</title>
@@ -200,6 +246,16 @@
<literal>VARBINARY</literal> types.
</para>
</listitem>
+
+ <listitem>
+ <para>
+ The result type of the <literal>GROUP_CONCAT()</literal>
+ function is now <literal>VARCHAR</literal> only if the the
+ value of the <literal>group_concat_max_len</literal> system
+ variable is less than or equal to 512. Otherwise, this
+ funciton returns a <literal>BLOB</literal>. (Bug #14169)
+ </para>
+ </listitem>
<listitem>
<para>
@@ -327,9 +383,9 @@
<listitem>
<para>
- Message for error 1109 changed from <literal>Unknown table ...
- in order clause</literal> to <literal>Unknown table '... in
- field list</literal>. (Bug #15091)
+ The message for error 1109 changed from <errortext>Unknown
+ table ... in order clause</errortext> to <errortext>Unknown
+ table ... in field list</errortext>. (Bug #15091)
</para>
</listitem>
@@ -369,6 +425,42 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ When using the <literal>GROUP_CONCAT()</literal> function
+ where the <literal>group_concat_max_len</literal> system
+ variable was greater than 512, the type of the result was
+ <literal>BLOB</literal> only if the query included an
+ <literal>ORDER BY</literal> clause; otherwise the result was a
+ <literal>VARCHAR</literal>. (Bug #14169)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The length of a <literal>VARCHAR()</literal> column that used
+ the <literal>utf8</literal> character set would increase each
+ time the table was re-created in a stored procedure or
+ prepared statement, eventually causing the <literal>CREATE
+ TABLE</literal> statement to fail. (Bug #13134)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>type_decimal</literal> failed with the prepared
+ statement protocol. (Bug #17826)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The MySQL server could crash with out of memory errors when
+ performing aggregate functions on a <literal>DECIMAL</literal>
+ column. (Bug #17602)
+ </para>
+ </listitem>
<listitem>
<para>
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-03-04 04:11:22 UTC (rev 1512)
+++ trunk/refman-common/news-5.1.xml 2006-03-04 09:28:38 UTC (rev 1513)
@@ -300,6 +300,24 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ The length of a <literal>VARCHAR()</literal> column that used
+ the <literal>utf8</literal> character set would increase each
+ time the table was re-created in a stored procedure or
+ prepared statement, eventually causing the <literal>CREATE
+ TABLE</literal> statement to fail. (Bug #13134)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The MySQL server could crash with out of memory errors when
+ performing aggregate functions on a <literal>DECIMAL</literal>
+ column. (Bug #17602)
+ </para>
+ </listitem>
<listitem>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1513 - in trunk: refman-5.0 refman-5.1 refman-common | jon | 4 Mar |
