Author: paul
Date: 2006-07-23 06:11:08 +0200 (Sun, 23 Jul 2006)
New Revision: 2807
Log:
r12684@frost: paul | 2006-07-22 23:10:37 -0500
Document bugfixes:
Bug#15195
Bug#15217
Bug#16110
Bug#16302
Bug#16494
Bug#16832
Bug#17203
Bug#17308
Bug#18080
Bug#19479
Bug#19764
Bug#20392
Modified:
trunk/refman-4.1/client-utility-programs.xml
trunk/refman-5.0/client-utility-programs.xml
trunk/refman-5.0/database-administration.xml
trunk/refman-5.0/storage-engines.xml
trunk/refman-5.1/client-utility-programs.xml
trunk/refman-common/news-4.1.xml
trunk/refman-common/news-5.0.xml
trunk/refman-common/news-5.1.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:11840
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:12648
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:8441
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:11840
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:12684
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:8441
Modified: trunk/refman-4.1/client-utility-programs.xml
===================================================================
--- trunk/refman-4.1/client-utility-programs.xml 2006-07-22 17:53:45 UTC (rev 2806)
+++ trunk/refman-4.1/client-utility-programs.xml 2006-07-23 04:11:08 UTC (rev 2807)
Changed blocks: 1, Lines Added: 6, Lines Deleted: 1; 954 bytes
@@ -12088,7 +12088,12 @@
<para>
These options have the same meaning as the corresponding
- clauses for <literal>LOAD DATA INFILE</literal>. See
+ clauses for <literal>LOAD DATA INFILE</literal>. For
+ example, to import Windows files that have lines
+ terminated with carriage return/linefeed pairs, use
+ <option>--lines-terminated-by="\r\n"</option>. (You might
+ have to double the backslashes, depending on the escaping
+ conventions of your command interpreter.) See
<xref linkend="load-data"/>.
</para>
</listitem>
Modified: trunk/refman-5.0/client-utility-programs.xml
===================================================================
--- trunk/refman-5.0/client-utility-programs.xml 2006-07-22 17:53:45 UTC (rev 2806)
+++ trunk/refman-5.0/client-utility-programs.xml 2006-07-23 04:11:08 UTC (rev 2807)
Changed blocks: 1, Lines Added: 6, Lines Deleted: 1; 954 bytes
@@ -12306,7 +12306,12 @@
<para>
These options have the same meaning as the corresponding
- clauses for <literal>LOAD DATA INFILE</literal>. See
+ clauses for <literal>LOAD DATA INFILE</literal>. For
+ example, to import Windows files that have lines
+ terminated with carriage return/linefeed pairs, use
+ <option>--lines-terminated-by="\r\n"</option>. (You might
+ have to double the backslashes, depending on the escaping
+ conventions of your command interpreter.) See
<xref linkend="load-data"/>.
</para>
</listitem>
Modified: trunk/refman-5.0/database-administration.xml
===================================================================
--- trunk/refman-5.0/database-administration.xml 2006-07-22 17:53:45 UTC (rev 2806)
+++ trunk/refman-5.0/database-administration.xml 2006-07-23 04:11:08 UTC (rev 2807)
Changed blocks: 1, Lines Added: 31, Lines Deleted: 0; 1694 bytes
@@ -2311,6 +2311,37 @@
<para>
<indexterm>
<primary>mysqld</primary>
+ <secondary>skip-merge option</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>skip-merge option</primary>
+ <secondary>mysqld</secondary>
+ </indexterm>
+
+ <option>--skip-merge</option>
+ </para>
+
+ <para>
+ Disable the <literal>MERGE</literal> storage engine. This
+ option was added in MySQL 5.0.24. It can be used if the
+ following behavior is undesirable: If a user has access to
+ <literal>MyISAM</literal> table
+ <replaceable>t</replaceable>, that user can create a
+ <literal>MERGE</literal> table
+ <replaceable>m</replaceable> that accesses
+ <replaceable>t</replaceable>. However, if the user's
+ privileges on <replaceable>t</replaceable> are
+ subsequently revoked, the user can continue to access
+ <replaceable>t</replaceable> by doing so through
+ <replaceable>m</replaceable>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <indexterm>
+ <primary>mysqld</primary>
<secondary>skip-name-resolve option</secondary>
</indexterm>
Modified: trunk/refman-5.0/storage-engines.xml
===================================================================
--- trunk/refman-5.0/storage-engines.xml 2006-07-22 17:53:45 UTC (rev 2806)
+++ trunk/refman-5.0/storage-engines.xml 2006-07-23 04:11:08 UTC (rev 2807)
Changed blocks: 1, Lines Added: 16, Lines Deleted: 0; 1347 bytes
@@ -1672,6 +1672,22 @@
</para>
<para>
+ <emphasis role="bold">Note</emphasis>: The use of
+ <literal>MERGE</literal> tables entails the following security
+ issue: If a user has access to <literal>MyISAM</literal> table
+ <replaceable>t</replaceable>, that user can create a
+ <literal>MERGE</literal> table <replaceable>m</replaceable> that
+ accesses <replaceable>t</replaceable>. However, if the user's
+ privileges on <replaceable>t</replaceable> are subsequently
+ revoked, the user can continue to access
+ <replaceable>t</replaceable> by doing so through
+ <replaceable>m</replaceable>. If this behavior is undesirable, you
+ can start the server with the new <option>--skip-merge</option>
+ option to disable the <literal>MERGE</literal> storage engine.
+ This option is available as of MySQL 5.0.24.
+ </para>
+
+ <para>
If you <literal>DROP</literal> the <literal>MERGE</literal> table,
you are dropping only the <literal>MERGE</literal> specification.
The underlying tables are not affected.
Modified: trunk/refman-5.1/client-utility-programs.xml
===================================================================
--- trunk/refman-5.1/client-utility-programs.xml 2006-07-22 17:53:45 UTC (rev 2806)
+++ trunk/refman-5.1/client-utility-programs.xml 2006-07-23 04:11:08 UTC (rev 2807)
Changed blocks: 1, Lines Added: 6, Lines Deleted: 1; 954 bytes
@@ -12251,7 +12251,12 @@
<para>
These options have the same meaning as the corresponding
- clauses for <literal>LOAD DATA INFILE</literal>. See
+ clauses for <literal>LOAD DATA INFILE</literal>. For
+ example, to import Windows files that have lines
+ terminated with carriage return/linefeed pairs, use
+ <option>--lines-terminated-by="\r\n"</option>. (You might
+ have to double the backslashes, depending on the escaping
+ conventions of your command interpreter.) See
<xref linkend="load-data"/>.
</para>
</listitem>
Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml 2006-07-22 17:53:45 UTC (rev 2806)
+++ trunk/refman-common/news-4.1.xml 2006-07-23 04:11:08 UTC (rev 2807)
Changed blocks: 1, Lines Added: 9, Lines Deleted: 0; 858 bytes
@@ -190,6 +190,15 @@
<listitem>
<para>
+ Using <literal>ANY</literal> with <quote>non-table</quote>
+ subqueries such as <literal>SELECT 1</literal> yields results
+ under certain circumstances due to incorrect application of
+ <literal>MIN()/MAX()</literal> optimization. (Bug #16302)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
The use of <literal>WHERE <replaceable>col_name</replaceable>
IS NULL</literal> in <literal>SELECT</literal> statements
reset the value of <literal>LAST_INSERT_ID()</literal> to
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2006-07-22 17:53:45 UTC (rev 2806)
+++ trunk/refman-common/news-5.0.xml 2006-07-23 04:11:08 UTC (rev 2807)
Changed blocks: 4, Lines Added: 100, Lines Deleted: 0; 4693 bytes
@@ -214,6 +214,15 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ The <literal>VIEW_DEFINITION</literal> column of the
+ <literal>INFORMATION_SCHEMA</literal> <literal>VIEWS</literal>
+ table now contains information about the view algorithm. (Bug
+ #16832)
+ </para>
+ </listitem>
+
</itemizedlist>
<para>
@@ -335,6 +344,24 @@
<listitem>
<para>
+ Using <literal>ANY</literal> with <quote>non-table</quote>
+ subqueries such as <literal>SELECT 1</literal> yields results
+ under certain circumstances due to incorrect application of
+ <literal>MIN()/MAX()</literal> optimization. (Bug #16302)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ When a row was inserted through a view but did not specify a
+ value for a column that had no default value in the base
+ table, no warning or error occurred. Now a warning occurs, or
+ an error in strict SQL mode. (Bug #16110)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
The use of <literal>WHERE <replaceable>col_name</replaceable>
IS NULL</literal> in <literal>SELECT</literal> statements
reset the value of <literal>LAST_INSERT_ID()</literal> to
@@ -566,10 +593,57 @@
Bugs fixed:
</para>
+ <remark role="note">
+ Leave security fixes first in the list.
+ </remark>
+
<itemizedlist>
<listitem>
<para>
+ <emphasis role="bold">Security fix</emphasis>: If a user has
+ access to <literal>MyISAM</literal> table
+ <replaceable>t</replaceable>, that user can create a
+ <literal>MERGE</literal> table <replaceable>m</replaceable>
+ that accesses <replaceable>t</replaceable>. However, if the
+ user's privileges on <replaceable>t</replaceable> are
+ subsequently revoked, the user can continue to access
+ <replaceable>t</replaceable> by doing so through
+ <replaceable>m</replaceable>. If this behavior is undesirable,
+ you can start the server with the new
+ <option>--skip-merge</option> option to disable the
+ <literal>MERGE</literal> storage engine. (Bug #15195)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>SELECT @@INSERT_ID</literal> displayed a value
+ unrelated to a preceding <literal>SET INSERT_ID</literal>. (It
+ was returning <literal>LAST_INSERT_ID</literal> instead.) (Bug
+ #20392)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Updating a column of a <literal>FEDERATED</literal> table to
+ <literal>NULL</literal> sometimes failed. (Bug #16494)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Performing <literal>INSERT ... SELECT ... JOIN ...
+ USING</literal> without qualifying the column names caused
+ <literal>ERROR 1052 "column 'x' in field list is
+ ambiguous"</literal> even in cases where the column references
+ were unambiguous. (Bug #18080)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
MySQL 5.0.23 contained a fix for Bug #10952 that has been
reverted in 5.0.24 because it introduced the risk of
unintended data loss.
@@ -794,6 +868,32 @@
<listitem>
<para>
+ Re-executing a stored procedure with a complex stored
+ procedure cursor query could lead to a server crash. (Bug
+ #15217)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Views created from prepared statements inside of stored
+ procedures were created with a definition that included both
+ <literal>SQL_CACHE</literal> and
+ <literal>SQL_NO_CACHE</literal>. (Bug #17203)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysqldump</command> did not dump the table name
+ correctly for some table identifiers that contained unusual
+ characters such as ‘<literal>:</literal>’. (Bug
+ #19479)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<command>mysqldump</command> would not dump views that had
become invalid because a table named in the view definition
had been dropped. Instead, it quit with an error message. Now
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-07-22 17:53:45 UTC (rev 2806)
+++ trunk/refman-common/news-5.1.xml 2006-07-23 04:11:08 UTC (rev 2807)
Changed blocks: 3, Lines Added: 36, Lines Deleted: 2; 2035 bytes
@@ -264,7 +264,7 @@
monitoring of what the server is actually doing. This is
because <literal>SHOW STATUS</literal> creates temporary
tables that may affect performance if it is called excessively
- often.
+ often. (Bug #10210, Bug #19764)
</para>
</listitem>
@@ -292,7 +292,7 @@
</para>
<remark role="note">
- Leave any imcompatible fixes first in the list.
+ Leave any incompatible fixes first in the list.
</remark>
<itemizedlist>
@@ -320,6 +320,40 @@
<listitem>
<para>
+ Re-executing a stored procedure with a complex stored
+ procedure cursor query could lead to a server crash. (Bug
+ #15217)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Views created from prepared statements inside of stored
+ procedures were created with a definition that included both
+ <literal>SQL_CACHE</literal> and
+ <literal>SQL_NO_CACHE</literal>. (Bug #17203)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Updating a column of a <literal>FEDERATED</literal> table to
+ <literal>NULL</literal> sometimes failed. (Bug #16494)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Performing <literal>INSERT ... SELECT ... JOIN ...
+ USING</literal> without qualifying the column names caused
+ <literal>ERROR 1052 "column 'x' in field list is
+ ambiguous"</literal> even in cases where the column references
+ were unambiguous. (Bug #18080)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Closing of temporary tables failed if binary logging was not
enabled. (Bug #20919)
</para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r2807 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-common | paul | 23 Jul |
