Author: paul
Date: 2007-06-09 19:35:24 +0200 (Sat, 09 Jun 2007)
New Revision: 6742
Log:
r26126@polar: paul | 2007-06-09 12:34:31 -0500
Reorder some changelog entries so that security fixes appear
first in the list.
Modified:
trunk/refman-5.0/releasenotes-es-5.0.xml
trunk/refman-5.1/news-5.1.xml
trunk/refman-common/TEMPLATE.news.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:26116
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:21265
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:17792
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:26126
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:21265
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:17792
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-06-09 15:43:05 UTC (rev 6741)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-06-09 17:35:24 UTC (rev 6742)
Changed blocks: 2, Lines Added: 59, Lines Deleted: 54; 6247 bytes
@@ -63,59 +63,89 @@
Bugs fixed:
</para>
+ <remark role="note">
+ Leave any security or incompatible fixes first in the list.
+ </remark>
+
<itemizedlist>
-
+
<listitem>
<para>
- When dumping procedures, <command>mysqldump <option>--compact</option></command>
- generated output that restored the session variable <literal>SQL_MODE</literal>
- without first capturing it. When dumping routines,
- <command>mysqldump <option>--compact</option></command> neither set
- nor retrieved the value of <literal>SQL_MODE</literal>.
- (Bug #28223)
+ <emphasis role="bold">Security Fix</emphasis>: <literal>CREATE
+ TABLE LIKE</literal> did not require any privileges on the
+ source table. (Bug #25578)
</para>
+
+ <para>
+ In addition, <literal>CREATE TABLE LIKE</literal> was not
+ isolated from alteration by other connections, which resulted
+ in various errors and incorrect binary log order when trying
+ to execute concurrently a <literal>CREATE TABLE LIKE</literal>
+ statement and either DDL statements on the source table or DML
+ or DDL statements on the target table. (Bug #23667)
+ </para>
</listitem>
-
+
<listitem>
<para>
- Attempting to <literal>LOAD_FILE</literal> from an
- empty floppy drive under Windows, caused the server to hang.
- For example, if you opened a connection to the server and
- then issued the command <command>SELECT LOAD_FILE('a:test');</command>,
- with no floppy in the drive, the server was inaccessible
- until the modal pop-up dialog box was dismissed.
- (Bug #28366)
+ <literal>NDB Cluster</literal>: When an API node sent more
+ than 1024 signals in a single batch, <literal>NDB</literal>
+ would process only the first 1024 of these, and then hang.
+ (Bug #28443)
</para>
</listitem>
-
+
<listitem>
<para>
- <command>mysqldump</command> calculated the required memory
- for a hex-blob string incorrectly causing a buffer
- overrun. This in turn caused <command>mysqldump</command>
- to crash silently and produce incomplete output. (Bug #28522)
+ <literal>NDB Cluster</literal>: A failure to release internal
+ resources following an error could lead to problems with
+ single user mode. (Bug #25818)
</para>
</listitem>
<listitem>
<para>
- <emphasis role="bold">Security Fix</emphasis>: <literal>CREATE
- TABLE LIKE</literal> did not require any privileges on the
- source table. (Bug #25578)
+ <literal>NDB Cluster</literal>: A delay in obtaining
+ <literal>AUTO_INCREMENT</literal> IDs could lead to excess
+ temporary errors. (Bug #28410)
</para>
+ </listitem>
+ <listitem>
<para>
- In addition, <literal>CREATE TABLE LIKE</literal> was not
- isolated from alteration by other connections, which resulted
- in various errors and incorrect binary log order when trying
- to execute concurrently a <literal>CREATE TABLE LIKE</literal>
- statement and either DDL statements on the source table or DML
- or DDL statements on the target table. (Bug #23667)
+ When dumping procedures, <command>mysqldump
+ <option>--compact</option></command> generated output that
+ restored the session variable <literal>SQL_MODE</literal>
+ without first capturing it. When dumping routines,
+ <command>mysqldump <option>--compact</option></command>
+ neither set nor retrieved the value of
+ <literal>SQL_MODE</literal>. (Bug #28223)
</para>
</listitem>
<listitem>
<para>
+ Attempting to <literal>LOAD_FILE</literal> from an empty
+ floppy drive under Windows, caused the server to hang. For
+ example, if you opened a connection to the server and then
+ issued the command <command>SELECT
+ LOAD_FILE('a:test');</command>, with no floppy in the drive,
+ the server was inaccessible until the modal pop-up dialog box
+ was dismissed. (Bug #28366)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysqldump</command> calculated the required memory
+ for a hex-blob string incorrectly causing a buffer overrun.
+ This in turn caused <command>mysqldump</command> to crash
+ silently and produce incomplete output. (Bug #28522)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
The query <literal>SELECT '2007-01-01' + INTERVAL
<replaceable>column_name</replaceable> DAY FROM
<replaceable>table_name</replaceable></literal> caused
@@ -165,31 +195,6 @@
<listitem>
<para>
- <literal>NDB Cluster</literal>: When an API node sent more
- than 1024 signals in a single batch, <literal>NDB</literal>
- would process only the first 1024 of these, and then hang.
- (Bug #28443)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <literal>NDB Cluster</literal>: A failure to release internal
- resources following an error could lead to problems with
- single user mode. (Bug #25818)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <literal>NDB Cluster</literal>: A delay in obtaining
- <literal>AUTO_INCREMENT</literal> IDs could lead to excess
- temporary errors. (Bug #28410)
- </para>
- </listitem>
-
- <listitem>
- <para>
Running <literal>CHECK TABLE</literal> concurrently with a
<literal>SELECT</literal>, <literal>INSERT</literal> or other
statement on Windows could corrupt a MyISAM table. (Bug
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-06-09 15:43:05 UTC (rev 6741)
+++ trunk/refman-5.1/news-5.1.xml 2007-06-09 17:35:24 UTC (rev 6742)
Changed blocks: 6, Lines Added: 59, Lines Deleted: 50; 5437 bytes
@@ -123,28 +123,11 @@
Bugs fixed:
</para>
+ <remark role="note">
+ Leave any security or incompatible fixes first in the list.
+ </remark>
+
<itemizedlist>
-
- <listitem>
- <para>
- Attempting to <literal>LOAD_FILE</literal> from an
- empty floppy drive under Windows, caused the server to hang.
- For example, if you opened a connection to the server and
- then issued the command <command>SELECT LOAD_FILE('a:test');</command>,
- with no floppy in the drive, the server was inaccessible
- until the modal pop-up dialog box was dismissed.
- (Bug #28366)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <command>mysqldump</command> calculated the required memory
- for a hex-blob string incorrectly causing a buffer
- overrun. This in turn caused <command>mysqldump</command>
- to crash silently and produce incomplete output. (Bug #28522)
- </para>
- </listitem>
<listitem>
<para>
@@ -165,6 +148,35 @@
<listitem>
<para>
+ <literal>NDB Cluster</literal> (Replication): A replicated
+ unique key allowed duplicate key inserts on the slave. (Bug
+ #27044)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Attempting to <literal>LOAD_FILE</literal> from an empty
+ floppy drive under Windows, caused the server to hang. For
+ example, if you opened a connection to the server and then
+ issued the command <command>SELECT
+ LOAD_FILE('a:test');</command>, with no floppy in the drive,
+ the server was inaccessible until the modal pop-up dialog box
+ was dismissed. (Bug #28366)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysqldump</command> calculated the required memory
+ for a hex-blob string incorrectly causing a buffer overrun.
+ This in turn caused <command>mysqldump</command> to crash
+ silently and produce incomplete output. (Bug #28522)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
The query <literal>SELECT '2007-01-01' + INTERVAL
<replaceable>column_name</replaceable> DAY FROM
<replaceable>table_name</replaceable></literal> caused
@@ -222,14 +234,6 @@
<listitem>
<para>
- <literal>NDB Cluster</literal> (Replication): A replicated
- unique key allowed duplicate key inserts on the slave. (Bug
- #27044)
- </para>
- </listitem>
-
- <listitem>
- <para>
Using <literal>CREATE TABLE LIKE ...</literal> would raise an
assertion when replicated to a slave. (Bug #18950)
</para>
@@ -437,18 +441,11 @@
Bugs fixed:
</para>
+ <remark role="note">
+ Leave any security or incompatible fixes first in the list.
+ </remark>
+
<itemizedlist>
-
- <listitem>
- <para>
- When dumping procedures, <command>mysqldump <option>--compact</option></command>
- generated output that restored the session variable <literal>SQL_MODE</literal>
- without first capturing it. When dumping routines,
- <command>mysqldump <option>--compact</option></command> neither set
- nor retrieved the value of <literal>SQL_MODE</literal>.
- (Bug #28223)
- </para>
- </listitem>
<listitem>
<para>
@@ -468,16 +465,6 @@
<listitem>
<para>
- The second execution of a prepared statement from a
- <literal>UNION</literal> query with <literal>ORDER BY
- RAND()</literal> caused the server to crash. This problem
- could also occur when invoking a stored procedure containing
- such a query. (Bug #27937)
- </para>
- </listitem>
-
- <listitem>
- <para>
<literal>NDB Cluster</literal>: When an API node sent more
than 1024 signals in a single batch, <literal>NDB</literal>
would process only the first 1024 of these, and then hang.
@@ -588,6 +575,28 @@
<listitem>
<para>
+ When dumping procedures, <command>mysqldump
+ <option>--compact</option></command> generated output that
+ restored the session variable <literal>SQL_MODE</literal>
+ without first capturing it. When dumping routines,
+ <command>mysqldump <option>--compact</option></command>
+ neither set nor retrieved the value of
+ <literal>SQL_MODE</literal>. (Bug #28223)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The second execution of a prepared statement from a
+ <literal>UNION</literal> query with <literal>ORDER BY
+ RAND()</literal> caused the server to crash. This problem
+ could also occur when invoking a stored procedure containing
+ such a query. (Bug #27937)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>CURDATE()</literal> is less than
<literal>NOW()</literal>, either when comparing
<literal>CURDATE()</literal> directly (<literal>CURDATE() <
Modified: trunk/refman-common/TEMPLATE.news.xml
===================================================================
--- trunk/refman-common/TEMPLATE.news.xml 2007-06-09 15:43:05 UTC (rev 6741)
+++ trunk/refman-common/TEMPLATE.news.xml 2007-06-09 17:35:24 UTC (rev 6742)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 0; 446 bytes
@@ -103,6 +103,10 @@
Bugs fixed:
</para>
+ <remark role="note">
+ Leave any security or incompatible fixes first in the list.
+ </remark>
+
<itemizedlist>
<listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r6742 - in trunk: . refman-5.0 refman-5.1 refman-common | paul | 9 Jun |
