Author: paul
Date: 2005-10-31 21:17:55 +0100 (Mon, 31 Oct 2005)
New Revision: 203
Log:
r233@kite-hub: paul | 2005-10-31 14:17:20 -0600
Document bugfixes:
Bug#4375
Bug#9505
Bug#12123
Bug#12166
Bug#12838
Bug#12925
Bug#12974
Bug#13347
Bug#13392
Bug#13551
Bug#13811
Bug#14009
Bug#14061
Bug#14138
Bug#14290
Bug#14388
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:3240
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:218
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:3240
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:233
Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml 2005-10-31 17:35:20 UTC (rev 202)
+++ trunk/refman-common/news-4.1.xml 2005-10-31 20:17:55 UTC (rev 203)
@@ -243,21 +243,83 @@
</remark>
<itemizedlist>
-
+
<listitem>
<para>
+ Use of <literal><replaceable>col_name</replaceable> =
+ VALUES(<replaceable>col_name</replaceable>)</literal> in the
+ <literal>ON DUPLICATE KEY UPDATE</literal> clause of an
+ <literal>INSERT</literal> statement failed with an
+ <literal>Column '<replaceable>col_name</replaceable>' in field
+ list is ambiguous</literal> error. (Bug #13392)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ On Windows, the server was not ignoring hidden or system
+ directories that Windows may have created in the data
+ directory, and would treat them as available databases. (Bug
+ #4375)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>LIKE</literal> operations did not work reliably for
+ the <literal>cp1250</literal> character set. (Bug #13347)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Maximum values were handled incorrectly for command-line
+ options of type <literal>GET_LL</literal>. (Bug #12925)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Use of <literal>WITH ROLLUP PROCEDURE ANALYSE()</literal>
+ could hang the server. (Bug #14138)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>ORDER BY
+ ABS(<replaceable>expr</replaceable>)</literal> could cause a
+ crash if <replaceable>expr</replaceable> was
+ <literal>NULL</literal>. (Bug #14009)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The example configuration files supplied with MySQL
+ distributions listed the <literal>thread_cache_size</literal>
+ variable as <literal>thread_cache</literal>. (Bug #13811)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>LOAD DATA INFILE</literal> would not accept the same
character for both the <literal>ESCAPED BY</literal> and the
<literal>ENCLOSED BY</literal> clauses. (Bug #11203)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Repeated transactions using
unique index lookups could cause a memory leak leading to
- error 288, <errortext>Out of index operations in transaction
- coordinator</errortext>. (Bug #14199)
+ error 288,
+
+ <errortext>Out of index operations in transaction
+ coordinator</errortext>
+
+ . (Bug #14199)
</para>
</listitem>
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2005-10-31 17:35:20 UTC (rev 202)
+++ trunk/refman-common/news-5.0.xml 2005-10-31 20:17:55 UTC (rev 203)
@@ -226,6 +226,110 @@
<listitem>
<para>
+ Use of <literal><replaceable>col_name</replaceable> =
+ VALUES(<replaceable>col_name</replaceable>)</literal> in the
+ <literal>ON DUPLICATE KEY UPDATE</literal> clause of an
+ <literal>INSERT</literal> statement failed with an
+ <literal>Column '<replaceable>col_name</replaceable>' in field
+ list is ambiguous</literal> error. (Bug #13392)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ On Windows, the server was not ignoring hidden or system
+ directories that Windows may have created in the data
+ directory, and would treat them as available databases. (Bug
+ #4375)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysqldump</command> could not dump views if the
+ <option>-x</option> option was given. (Bug #12838)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysqlimport</command> now issues a <literal>SET
+ @@character_set_database = binary</literal> statement before
+ loading data so that a file containing mixed character sets
+ (columns with different character sets) can be loaded
+ properly. (Bug #12123)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Use of the deprecated <option>--sql-bin-update-same</option>
+ option caused a server crash. (Bug #12974)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Maximum values were handled incorrectly for command-line
+ options of type <literal>GET_LL</literal>. (Bug #12925)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For a user that has the <literal>SELECT</literal> privilege on
+ a view, the server erroneously was also requiring the user to
+ have the <literal>EXECUTE</literal> privilege at view
+ execution time for stored functions used in the view
+ definition. (Bug #9505)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Use of <literal>WITH ROLLUP PROCEDURE ANALYSE()</literal>
+ could hang the server. (Bug #14138)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>ORDER BY
+ ABS(<replaceable>expr</replaceable>)</literal> could cause a
+ crash if <replaceable>expr</replaceable> was
+ <literal>NULL</literal>. (Bug #14009)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The example configuration files supplied with MySQL
+ distributions listed the <literal>thread_cache_size</literal>
+ variable as <literal>thread_cache</literal>. (Bug #13811)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using <literal>ALTER TABLE</literal> to add an index could
+ fail if the operation ran out of temporary file space. Now it
+ automatically makes a second attempt that uses a slower method
+ but no temporary file. In this case, problems that occurred
+ during the first attempt can be displayed with <literal>SHOW
+ WARNINGS</literal>. (Bug #12166)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The input polling loop for Instance Manager did not sleep
+ properly. Instance Manager used up too much CPU as a result.
+ (Bug #14388)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Trying to take the logarithm of a negative value is now
handled in the same fashion as division by zero. That is, it
produces a warning when
@@ -267,6 +371,15 @@
<listitem>
<para>
+ The displayed value for the
+ <literal>CHARACTER_MAXIMUM_LENGTH</literal> column in the
+ <literal>INFORMATION_SCHEMA.COLUMNS</literal> table was not
+ adjusted for multi-byte character sets. (Bug #14290)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
A bugfix in MySQL 5.0.15 caused the displayed values for the
<literal>CHARACTER_MAXIMUM_LENGTH</literal> and
<literal>CHARACTER_OCTET_LENGTH</literal> columns in the
@@ -633,14 +746,17 @@
<listitem>
<para>
+ <command>mysqldump</command> could not dump views. (Bug
+ #14061)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Using an undefined variable in an <literal>IF</literal> or
<literal>SET</literal> clause inside a stored routine produced
- an incorrect
-
- <errortext>unknown column ... in 'order
- clause'</errortext>
-
- error message. (Bug #13037)
+ an incorrect <literal>unknown column ... in 'order
+ clause'</literal> error message. (Bug #13037)
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r203 - in trunk: . refman-common | paul | 31 Oct |
