Author: paul
Date: 2006-05-31 03:43:13 +0200 (Wed, 31 May 2006)
New Revision: 2236
Log:
r10834@frost: paul | 2006-05-30 20:34:50 -0500
Document bugfixes:
Bug#17204
Bug#18282
Bug#18669
Bug#19815
Modified:
trunk/
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:10144
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:10787
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:7663
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:10144
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:10834
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:7663
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2006-05-30 20:46:13 UTC (rev 2235)
+++ trunk/refman-common/news-5.0.xml 2006-05-31 01:43:13 UTC (rev 2236)
@@ -192,7 +192,7 @@
</para>
<itemizedlist>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: The limit of 2048 ordered
@@ -201,7 +201,7 @@
<literal>AUTO_INCREMENT</literal> columns) that may be used.
(Bug #14509)
</para>
- </listitem>
+ </listitem>
<listitem>
<para>
@@ -412,6 +412,46 @@
<listitem>
<para>
+ If there is a global read lock, <literal>CREATE
+ DATABASE</literal>, <literal>RENAME DATABASE</literal>, and
+ <literal>DROP DATABASE</literal> could deadlock. (Bug #19815)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>COM_STATISTICS</literal> command was changed in
+ 5.0.3 to display session status variable values rather than
+ global values. This causes <command>mysqladmin
+ status</command> information not to be useful for the
+ <literal>Slow queries</literal> and <literal>Opens</literal>
+ values. Now <literal>COM_STATISTICS</literal> displays the
+ global values for <literal>Slow queries</literal> and
+ <literal>Opens</literal>. (Bug #18669)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>INFORMATION_SCHEMA.TABLES</literal> provided
+ inconsistent info about invalid views. This could cause server
+ crashes or result in incorrect data being returned for queries
+ that attempt to obtain information from
+ <literal>INFORMATION_SCHEMA</literal> tables about views using
+ stored functions. (Bug #18282)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Multiple calls to a stored procedure that selects from
+ <literal>INFORMATION_SCHEMA</literal> could cause a server
+ crash. (Bug #17204)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Premature optimization of nested subqueries in the
<literal>FROM</literal> clause that refer to aggregate
functions could lead to incorrect results. (Bug #19077)
@@ -905,8 +945,7 @@
<itemizedlist>
<listitem>
- <para>
- </para>
+ <para></para>
</listitem>
</itemizedlist>
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-05-30 20:46:13 UTC (rev 2235)
+++ trunk/refman-common/news-5.1.xml 2006-05-31 01:43:13 UTC (rev 2236)
@@ -57,7 +57,7 @@
</para>
<itemizedlist>
-
+
<listitem>
<para>
<emphasis role="bold">Incompatible change</emphasis>: The
@@ -67,18 +67,18 @@
database can now view, alter, or drop any events defined on
that database.
</para>
-
+
<para>
If you used scheduled events in an earlier MySQL 5.1 release,
- you should rename any of them having the same name and
- defined on the same database but belonging to different users
- — so that all events in a given database have unique
- names — <emphasis>before</emphasis> upgrading to 5.1.12
- (or newer).
+ you should rename any of them having the same name and defined
+ on the same database but belonging to different users —
+ so that all events in a given database have unique names
+ — <emphasis>before</emphasis> upgrading to 5.1.12 (or
+ newer).
</para>
-
+
<para>
- For additional information, see
+ For additional information, see
<xref linkend="events-privileges"/>.
</para>
</listitem>
@@ -194,7 +194,7 @@
<xref linkend="ssl-options"/>. (Bug#19606)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: The limit of 2048 ordered
@@ -203,7 +203,7 @@
<literal>AUTO_INCREMENT</literal> columns) that may be used.
(Bug #14509)
</para>
- </listitem>
+ </listitem>
<listitem>
<para>
@@ -257,15 +257,25 @@
<itemizedlist>
- <para>
- <literal>NDB Cluster</literal>: <literal>SELECT
- MIN(<replaceable>unique_column</replaceable>)</literal> from a
- Cluster table with user-defined partitioning crashed the server.
- (Bug #18730)
- </para>
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: <literal>SELECT
+ MIN(<replaceable>unique_column</replaceable>)</literal> from a
+ Cluster table with user-defined partitioning crashed the
+ server. (Bug #18730)
+ </para>
+ </listitem>
<listitem>
<para>
+ If there is a global read lock, <literal>CREATE
+ DATABASE</literal>, <literal>RENAME DATABASE</literal>, and
+ <literal>DROP DATABASE</literal> could deadlock. (Bug #19815)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Premature optimization of nested subqueries in the
<literal>FROM</literal> clause that refer to aggregate
functions could lead to incorrect results. (Bug #19077)
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r2236 - in trunk: . refman-common | paul | 31 May |
