Author: jstephens
Date: 2006-04-08 16:50:04 +0200 (Sat, 08 Apr 2006)
New Revision: 1767
Log:
Documenting bugfixes:
Server:
Bug #12076, Bug #14945, Bug #16248, Bug #16814, Bug #16827
Bug #17374, Bug #18281, Bug #18310, Bug #18321
Docs:
Bug #18588
Docs/Cluster:
Bug #15722
Modified:
trunk/refman-5.0/optimization.xml
trunk/refman-5.0/triggers.xml
trunk/refman-5.1/optimization.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/optimization.xml
===================================================================
--- trunk/refman-5.0/optimization.xml 2006-04-08 05:58:24 UTC (rev 1766)
+++ trunk/refman-5.0/optimization.xml 2006-04-08 14:50:04 UTC (rev 1767)
@@ -1591,6 +1591,13 @@
<programlisting>
SET engine_condition_pushdown=On;
</programlisting>
+
+ <para>
+ <emphasis role="bold">Note</emphasis>: Condition
+ pushdown is not supported for columns of any of the
+ <literal>BLOB</literal> or <literal>TEXT</literal>
+ types.
+ </para>
</listitem>
</itemizedlist>
Modified: trunk/refman-5.0/triggers.xml
===================================================================
--- trunk/refman-5.0/triggers.xml 2006-04-08 05:58:24 UTC (rev 1766)
+++ trunk/refman-5.0/triggers.xml 2006-04-08 14:50:04 UTC (rev 1767)
@@ -534,13 +534,26 @@
<emphasis role="bold">Note</emphasis>: Prior to MySQL 5.0.10, the
table name was required instead of the schema name
(<literal><replaceable>table_name</replaceable>.<replaceable>trigger_name</replaceable></literal>).
- When upgrading from a previous version of MySQL 5.0 to MySQL 5.0.10
- or newer, you must drop all triggers <emphasis>before
- upgrading</emphasis> and re-create them afterward, or else
+ When upgrading from a previous version of MySQL 5.0 to MySQL
+ 5.0.10 or newer, you must drop all triggers <emphasis>before
+ upgrading</emphasis> and re-create them afterwards, or else
<literal>DROP TRIGGER</literal> does not work after the upgrade.
See <xref linkend="upgrading-from-4-1"/>, for a suggested upgrade
procedure.
</para>
+
+ <para>
+ In addition, triggers created in MySQL 5.0.16 or later cannot be
+ dropped following a downgrade to MySQL 5.0.15 or earlier. If you
+ wish to perform such a downgrade, you must also in this case drop
+ all triggers <emphasis>prior to</emphasis> the downgrade, and then
+ re-create them afterwards.
+ </para>
+
+ <para>
+ (For more information about these two issues, see Bug #15921 and
+ Bug #18588.)
+ </para>
</section>
Modified: trunk/refman-5.1/optimization.xml
===================================================================
--- trunk/refman-5.1/optimization.xml 2006-04-08 05:58:24 UTC (rev 1766)
+++ trunk/refman-5.1/optimization.xml 2006-04-08 14:50:04 UTC (rev 1767)
@@ -1629,7 +1629,14 @@
<programlisting>
SET engine_condition_pushdown=On;
</programlisting>
- </listitem>
+
+ <para>
+ <emphasis role="bold">Note</emphasis>: Condition
+ pushdown is not supported for columns of any of the
+ <literal>BLOB</literal> or <literal>TEXT</literal>
+ types.
+ </para>
+ </listitem>
</itemizedlist>
</listitem>
Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml 2006-04-08 05:58:24 UTC (rev 1766)
+++ trunk/refman-common/news-4.1.xml 2006-04-08 14:50:04 UTC (rev 1767)
@@ -190,6 +190,42 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ The euro sign (<literal>€</literal>) was not stored
+ correctly in columns using the
+ <literal>latin1_german1_ci</literal> or
+ <literal>latin1_general_ci</literal> collation. (Bug #18321)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The server was always built as though
+ <option>--with-extra-charsets=complex</option> had been
+ specified. (Bug #12076)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>SELECT ... WHERE <replaceable>column</replaceable>
+ LIKE 'A%'</literal> when <replaceable>column</replaceable>
+ had a key and used the <literal>latin2_czech_cs</literal>
+ collation. (Bug #17374)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A query using WHERE (<replaceable>column_1</replaceable>,
+ <replaceable>column_2</replaceable>) IN
+ ((<replaceable>value_1</replaceable>,
+ <replaceable>value_2</replaceable>)[, (..., ...), ...]) would
+ return incorrect results. (Bug #16248)
+ </para>
+ </listitem>
<listitem>
<para>
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2006-04-08 05:58:24 UTC (rev 1766)
+++ trunk/refman-common/news-5.0.xml 2006-04-08 14:50:04 UTC (rev 1767)
@@ -211,6 +211,59 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ The euro sign (<literal>€</literal>) was not stored
+ correctly in columns using the
+ <literal>latin1_german1_ci</literal> or
+ <literal>latin1_general_ci</literal> collation. (Bug #18321)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>EXTRACT(QUARTER FROM
+ <replaceable>date</replaceable>)</literal> returned
+ unexpected results. (Bug #18100)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>TRUNCATE</literal> did not reset the
+ <literal>AUTO_INCREMENT</literal> counter for
+ <literal>MyISAM</literal> tables when issued inside a stored
+ procedure. (Bug #14945)
+ </para>
+
+ <para>
+ <emphasis role="bold">Note</emphasis>: This bug did not affect
+ <literal>InnoDB</literal> tables. Also,
+ <literal>TRUNCATE</literal> does not reset the
+ <literal>AUTO_INCREMENT</literal> counter for
+ <literal>NDBCluster</literal> tables regardless of when it is
+ called (see Bug #18864).
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The server was always built as though
+ <option>--with-extra-charsets=complex</option> had been
+ specified. (Bug #12076)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A query using WHERE (<replaceable>column_1</replaceable>,
+ <replaceable>column_2</replaceable>) IN
+ ((<replaceable>value_1</replaceable>,
+ <replaceable>value_2</replaceable>)[, (..., ...), ...]) would
+ return incorrect results. (Bug #16248)
+ </para>
+ </listitem>
<listitem>
<para>
@@ -278,6 +331,15 @@
</remark>
<itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>InnoDB</literal>: The <literal>InnoDB</literal>
+ storage engine now provides a descriptive error message if
+ <filename>ibdata</filename> file information is omitted from
+ <filename>my.cnf</filename>. (Bug #16827)
+ </para>
+ </listitem>
<listitem>
<para>
@@ -290,7 +352,7 @@
<listitem>
<para>
- Windows builds now have SSL support enabled. (Bug#18195)
+ Windows builds now have SSL support enabled. (Bug #18195)
</para>
</listitem>
@@ -315,11 +377,11 @@
<listitem>
<para>
- Security Improvement: Checks for permissions on database
- operations were performed in a case-insensitive manner,
- meaning that a user with permissions on database
- <literal>MYDATABASE</literal> also had permissions on database
- <literal>myDataBase</literal>. (Bug #17279)
+ <emphasis role="bold">Security Enhancement</emphasis>: Checks
+ for permissions on database operations were performed in a
+ case-insensitive manner, meaning that a user with permissions
+ on database <literal>MYDATABASE</literal> also had permissions
+ on database <literal>myDataBase</literal>. (Bug #17279)
</para>
</listitem>
@@ -330,6 +392,37 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>InnoDB</literal>: The <literal>LATEST FOREIGN KEY
+ ERROR</literal> section in the output of <literal>SHOW
+ INNODB STATUS</literal> was sometimes formatted
+ incorrectly, causing problems with scripts that parsed the
+ output of this statement. (Bug #16814)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ When using <literal>ORDER BY</literal> with a non-string
+ column inside <literal>GROUP_CONCAT()</literal> the result's
+ character set was converted to binary. (Bug #18281)
+ </para>
+
+ <para>
+ See also Bug #14169.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>SELECT ... WHERE <replaceable>column</replaceable>
+ LIKE 'A%'</literal> when <replaceable>column</replaceable>
+ had a key and used the <literal>latin2_czech_cs</literal>
+ collation. (Bug #17374)
+ </para>
+ </listitem>
<listitem>
<para>
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-04-08 05:58:24 UTC (rev 1766)
+++ trunk/refman-common/news-5.1.xml 2006-04-08 14:50:04 UTC (rev 1767)
@@ -192,6 +192,40 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>EXTRACT(QUARTER FROM
+ <replaceable>date</replaceable>)</literal> returned
+ unexpected results. (Bug #18100)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>TRUNCATE</literal> did not reset the
+ <literal>AUTO_INCREMENT</literal> counter for
+ <literal>MyISAM</literal> tables when issued inside a stored
+ procedure. (Bug #14945)
+ </para>
+
+ <para>
+ <emphasis role="bold">Note</emphasis>: This bug did not affect
+ <literal>InnoDB</literal> tables. Also,
+ <literal>TRUNCATE</literal> does not reset the
+ <literal>AUTO_INCREMENT</literal> counter for
+ <literal>NDBCluster</literal> tables regardless of when it is
+ called (see Bug #18864).
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The server was always built as though
+ <option>--with-extra-charsets=complex</option> had been
+ specified. (Bug #12076)
+ </para>
+ </listitem>
<listitem>
<para>
@@ -760,6 +794,23 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ The server would crash when <literal>SHOW STATUS</literal> was
+ called on a server linked with <literal>yaSSL</literal>. (Bug
+ #18310)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>SELECT ... WHERE <replaceable>column</replaceable>
+ LIKE 'A%'</literal> when <replaceable>column</replaceable>
+ had a key and used the <literal>latin2_czech_cs</literal>
+ collation. (Bug #17374)
+ </para>
+ </listitem>
<listitem>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1767 - in trunk: refman-5.0 refman-5.1 refman-common | jon | 8 Apr |
