Author: paul
Date: 2005-11-09 05:17:47 +0100 (Wed, 09 Nov 2005)
New Revision: 299
Log:
r3602@frost: paul | 2005-11-08 22:15:36 -0600
Document bugfixes:
Bug#9815
Bug#13126
Bug#13573
Bug#13814
Bug#13894
Bug#13941
Bug#14026
Bug#14056
Bug#14093
Bug#14210
Bug#14256
Bug#14466
Bug#14480
Bug#14537
Bug#14540
Bug#14672
Modified:
trunk/
trunk/refman-common/news-4.1.xml
trunk/refman-common/news-5.0.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:3578
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:340
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:3602
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:340
Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml 2005-11-09 01:07:24 UTC (rev 298)
+++ trunk/refman-common/news-4.1.xml 2005-11-09 04:17:47 UTC (rev 299)
@@ -246,6 +246,45 @@
<listitem>
<para>
+ <literal>CREATE TABLE <replaceable>tbl_name</replaceable>
+ (…) SELECT …</literal> could crash the server
+ and write invalid data into the <filename>.frm</filename> file
+ if the <literal>CREATE TABLE</literal> and
+ <literal>SELECT</literal> both contained a column with the
+ same name. (Bug #14480)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For <literal>MyISAM</literal> tables, incorrect query results
+ or incorrect updates could occur under these conditions: There
+ is a multiple-column index that includes a
+ <literal>BLOB</literal> column that is not the last column in
+ the index, and the statement performs a lookup on the index
+ using key column values that have <literal>NULL</literal> for
+ the <literal>BLOB</literal> column and that provide values for
+ all columns up to the <literal>BLOB</literal> column and at
+ least the next column in the index. (Bug #13814)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Deletes from a <literal>CSV</literal> table could cause table
+ corruption. (Bug #14672)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ An update of a <literal>CSV</literal> table could cause a
+ server crash. (Bug #13894)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<command>mysqld_safe</command> did not correctly start the
<literal>-max</literal> version of the server (if it was
present) if the <option>--ledir</option> option was given.
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2005-11-09 01:07:24 UTC (rev 298)
+++ trunk/refman-common/news-5.0.xml 2005-11-09 04:17:47 UTC (rev 299)
@@ -226,6 +226,117 @@
<listitem>
<para>
+ <literal>ORDER BY DESC</literal> within the
+ <literal>GROUP_CONCAT()</literal> function was not honored
+ when used in a view. (Bug #14466)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A comparison with an invalid date (such as <literal>WHERE
+ <replaceable>col_name</replaceable> >
+ '2005-09-31'</literal>) caused any index on
+ <replaceable>col_name</replaceable> not to be used and a
+ string comparison for each row, resulting in slow performance.
+ (Bug #14093)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Within stored routines, <literal>REPLACE()</literal> could
+ return an empty string (rather than the original string) when
+ no replacement was done, and <literal>IFNULL()</literal> could
+ return garbage results. (Bug #13941)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Inserts of too-large <literal>DECIMAL</literal> values were
+ handled inconsistently (sometimes set to the maximum
+ <literal>DECIMAL</literal> value, sometimes set to 0). (Bug
+ #13573)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Executing <literal>REPAIR TABLE</literal>, <literal>ANALYZE
+ TABLE</literal>, or <literal>OPTIMIZE TABLE</literal> on a
+ view for which an underlying table had been dropped caused a
+ server crash. (Bug #14540)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A prepared statement that selected from a view processed using
+ the merge algorithm could crash on the second execution. (Bug
+ #14026)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Deletes from a <literal>CSV</literal> table could cause table
+ corruption. (Bug #14672)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ An update of a <literal>CSV</literal> table could cause a
+ server crash. (Bug #13894)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For queries with nested outer joins, the optimizer could
+ choose join orders that query execution could not handle. The
+ fix is that now the optimizer avoids choosing such join
+ orders. (Bug #13126)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Starting <command>mysqld</command> with the
+ <option>--skip-innodb</option> and
+ <option>--default-storage-engine=innodb</option> (or
+ <option>--default-table-type=innodb</option> caused a server
+ crash. (Bug #9815, re-fix of bug from 5.0.5)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysqlmanager</command> did not start up correctly on
+ Windows 2003. (Bug #14537)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The parser did not correctly recognize wildcards in the host
+ part of the <literal>DEFINER</literal> user in <literal>CREATE
+ VIEW</literal> statements. (Bug #14256)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Memory corruption and a server crash could be caused by
+ statements that used a cursor and generated a result set
+ larger than <literal>max_heap_table_size</literal>. (Bug
+ #14210)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<command>mysqld_safe</command> did not correctly start the
<literal>-max</literal> version of the server (if it was
present) if the <option>--ledir</option> option was given.
@@ -801,6 +912,15 @@
<listitem>
<para>
+ For <literal>InnoDB</literal> tables, using a column prefix
+ for a <literal>utf8</literal> column in a primary key caused
+ <literal>Cannot find record</literal> errors when attempting
+ to locate records. (Bug #14056)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
An expression in an <literal>ORDER BY</literal> clause failed
with <literal>Unknown column
'<replaceable>col_name</replaceable>' in 'order
@@ -1671,10 +1791,10 @@
<listitem>
<para>
- <emphasis role="bold">Incompatible change:</emphasis>
- A lock wait timeout caused <literal>InnoDB</literal> to roll
- back the entire current transaction. Now it rolls back only
- the most recent SQL statement. (Bug #12308)
+ <emphasis role="bold">Incompatible change:</emphasis> A lock
+ wait timeout caused <literal>InnoDB</literal> to roll back the
+ entire current transaction. Now it rolls back only the most
+ recent SQL statement. (Bug #12308)
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r299 - in trunk: . refman-common | paul | 9 Nov |
