Author: paul
Date: 2006-02-14 04:34:48 +0100 (Tue, 14 Feb 2006)
New Revision: 1306
Log:
r7459@frost: paul | 2006-02-13 21:33:23 -0600
Document bugfixes:
Bug#6536
Bug#9680
Bug#12019
Bug#14496
Bug#14851
Bug#15166
Bug#15196
Bug#15562
Bug#15588
Bug#15805
Bug#16511
Modified:
trunk/
trunk/refman-common/news-4.1.xml
trunk/refman-common/news-5.0.xml
trunk/refman-common/news-5.1.xml
trunk/refman-common/news-myodbc.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:7420
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:3045
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:7459
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:3045
Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml 2006-02-14 01:11:18 UTC (rev 1305)
+++ trunk/refman-common/news-4.1.xml 2006-02-14 03:34:48 UTC (rev 1306)
@@ -186,6 +186,37 @@
<listitem>
<para>
+ Binary distributions for Solaris contained files with group
+ ownership set to the non-existing <literal>wheel</literal>
+ group. Now the <literal>bin</literal> group is used. (Bug
+ #15562)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Killing a long-running query containing a subquery could cause
+ a server crash. (Bug #14851)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Repeated invocation of <literal>my_init()</literal> and
+ <literal>my_end()</literal> caused corruption of character set
+ data and connection failure. (Bug #6536)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A <literal>FULLTEXT</literal> query in a prepared statement
+ could result in unexpected behavior. (Bug #14496)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
A <literal>FULLTEXT</literal> query in a
<literal>UNION</literal> could result in unexpected behavior.
(Bug #16893)
@@ -395,6 +426,14 @@
<listitem>
<para>
+ <literal>CAST(... AS TIME)</literal> operations returned
+ different results when using versus not using
+ prepared-statement protocol. (Bug #15805)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Performing a <literal>RENAME TABLE</literal> on an InnoDB
table when the server is started with the
<literal>--innodb-file-per-table</literal> and the data
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2006-02-14 01:11:18 UTC (rev 1305)
+++ trunk/refman-common/news-5.0.xml 2006-02-14 03:34:48 UTC (rev 1306)
@@ -294,6 +294,65 @@
<listitem>
<para>
+ Binary distributions for Solaris contained files with group
+ ownership set to the non-existing <literal>wheel</literal>
+ group. Now the <literal>bin</literal> group is used. (Bug
+ #15562)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>DECIMAL</literal> data type was not being handled
+ correctly with prepared statements. (Bug #16511)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>SELECT</literal> privilege was being required
+ even for triggers that performed no selects. (Bug #15196)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>UPDATE</literal> privilege was being required
+ even for triggers that performed no updates. (Bug #15166)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>CAST(... AS TIME)</literal> operations returned
+ different results when using versus not using
+ prepared-statement protocol. (Bug #15805)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Improper memory handling for stored routine variables could
+ cause memory overruns and binary log corruption. (Bug #15588)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Killing a long-running query containing a subquery could cause
+ a server crash. (Bug #14851)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A <literal>FULLTEXT</literal> query in a prepared statement
+ could result in unexpected behavior. (Bug #14496)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
A <literal>RETURN</literal> statement within a trigger caused
a server crash. <literal>RETURN</literal> now is disallowed
within triggers. To exit immediately, use
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-02-14 01:11:18 UTC (rev 1305)
+++ trunk/refman-common/news-5.1.xml 2006-02-14 03:34:48 UTC (rev 1306)
@@ -91,6 +91,42 @@
<listitem>
<para>
+ The <literal>SELECT</literal> privilege was being required
+ even for triggers that performed no selects. (Bug #15196)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>UPDATE</literal> privilege was being required
+ even for triggers that performed no updates. (Bug #15166)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>CAST(... AS TIME)</literal> operations returned
+ different results when using versus not
+ using prepared-statement protocol. (Bug #15805)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Killing a long-running query containing a subquery could cause
+ a server crash. (Bug #14851)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>InnoDB</literal> could display an incorrect error
+ message for a cascading update. (Bug #9680)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
A <literal>RETURN</literal> statement within a trigger caused
a server crash. <literal>RETURN</literal> now is disallowed
within triggers. To exit immediately, use
@@ -343,6 +379,20 @@
<listitem>
<para>
+ Improper memory handling for stored routine variables could
+ cause memory overruns and binary log corruption. (Bug #15588)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A <literal>FULLTEXT</literal> query in a prepared statement
+ could result in unexpected behavior. (Bug #14496)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>STR_TO_DATE(1,NULL)</literal> caused a server crash.
(Bug #15828)
</para>
Modified: trunk/refman-common/news-myodbc.xml
===================================================================
--- trunk/refman-common/news-myodbc.xml 2006-02-14 01:11:18 UTC (rev 1305)
+++ trunk/refman-common/news-myodbc.xml 2006-02-14 03:34:48 UTC (rev 1306)
@@ -75,6 +75,12 @@
<listitem>
<para>
+ File DSNs could not be saved. (Bug #12019)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>SQLColumns()</literal> returned no information for
tables that had a column named using a reserved word. (Bug
#9539)
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1306 - in trunk: . refman-common | paul | 14 Feb |
