Below is the list of changes that have just been committed into a local
mysqldoc repository of stefan. When stefan does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://www.mysql.com/doc/I/n/Installing_source_tree.html
ChangeSet
1.2993 05/07/12 00:31:38 stefan@stripped +2 -0
Merge bk://mysqldoc@stripped
into apollon.site:/home/stefan/bk/mysqldoc
refman-5.0/news.xml
1.48 05/07/12 00:31:37 stefan@stripped +0 -0
Auto merged
refman/news.xml
1.53 05/07/12 00:31:36 stefan@stripped +0 -0
Auto merged
# This is a BitKeeper patch. What follows are the unified diffs for the
# set of deltas contained in the patch. The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User: stefan
# Host: apollon.site
# Root: /home/stefan/bk/mysqldoc/RESYNC
--- 1.47/refman-5.0/news.xml 2005-07-11 16:05:40 +02:00
+++ 1.48/refman-5.0/news.xml 2005-07-12 00:31:37 +02:00
@@ -630,6 +630,50 @@
Thanks!
-->
+<!--
+ Leave the security fix item as first in the list so it stands out better
+-->
+
+ <listitem><para>
+ <emphasis role="bold">Security fix</emphasis>: On Windows systems,
+ a user with any of the following privileges
+
+ <itemizedlist>
+
+ <listitem><para>
+ <literal>REFERENCES</literal>
+ </para></listitem>
+
+ <listitem><para>
+ <literal>CREATE TEMPORARY TABLES</literal>
+ </para></listitem>
+
+ <listitem><para>
+ <literal>GRANT OPTION</literal>
+ </para></listitem>
+
+ <listitem><para>
+ <literal>CREATE</literal>
+ </para></listitem>
+
+ <listitem><para>
+ <literal>SELECT</literal>
+ </para></listitem>
+
+ </itemizedlist>
+
+ on <literal>*.*</literal> could crash <literal>mysqld</literal> by
+ issuing a <literal>USE LPT1;</literal> or <literal>USE
+ PRN;</literal> command. In addition, any of the commands
+ <literal>USE NUL;</literal>, <literal>USE CON;</literal>,
+ <literal>USE COM1;</literal>, or <literal>USE AUX;</literal> would
+ report success even though the database was not in fact changed.
+ <emphasis role="bold">Note</emphasis>: Although this bug was
+ thought to be fixed previously, it was later discovered to be
+ present in the MySQL 5.0.7-beta release for Windows. (Bug #9148,
+ <ulink url="http://cve.mitre.org/cvename.cgi?name=CAN-2005-0799">CAN-2005-0799</ulink>
+ </para></listitem>
+
<listitem><para>
<literal>mysqld_safe</literal> would sometimes fail to remove the
pid file for the old <literal>mysql</literal> process after a
@@ -703,46 +747,6 @@
</para></listitem>
<listitem><para>
- <emphasis role="bold">Security fix</emphasis>: On Windows systems,
- a user with any of the following privileges
-
- <itemizedlist>
-
- <listitem><para>
- <literal>REFERENCES</literal>
- </para></listitem>
-
- <listitem><para>
- <literal>CREATE TEMPORARY TABLES</literal>
- </para></listitem>
-
- <listitem><para>
- <literal>GRANT OPTION</literal>
- </para></listitem>
-
- <listitem><para>
- <literal>CREATE</literal>
- </para></listitem>
-
- <listitem><para>
- <literal>SELECT</literal>
- </para></listitem>
-
- </itemizedlist>
-
- on <literal>*.*</literal> could crash <literal>mysqld</literal> by
- issuing a <literal>USE LPT1;</literal> or <literal>USE
- PRN;</literal> command. In addition, any of the commands
- <literal>USE NUL;</literal>, <literal>USE CON;</literal>,
- <literal>USE COM1;</literal>, or <literal>USE AUX;</literal> would
- report success even though the database was not in fact changed.
- <emphasis role="bold">Note</emphasis>: Although this bug was
- thought to be fixed previously, it was later discovered to be
- present in the MySQL 5.0.7-beta release for Windows. (Bug #9148,
- <ulink url="http://cve.mitre.org/cvename.cgi?name=CAN-2005-0799">CAN-2005-0799</ulink>
- </para></listitem>
-
- <listitem><para>
An issue with index merging could cause suboptimal index merge
plans to be chosen when searching by indexes created on
<literal>DATE</literal> columns. The same issue caused the InnoDB
@@ -1101,9 +1105,9 @@
<itemizedlist>
- <listitem><para>
- Triggers with dropped functions caused crashes. (Bug #5893)
- </para></listitem>
+<!--
+ Leave the security fix item as first in the list so it stands out better
+-->
<listitem><para>
<emphasis role="bold">Security update</emphasis>: A user with
@@ -1114,6 +1118,10 @@
</para></listitem>
<listitem><para>
+ Triggers with dropped functions caused crashes. (Bug #5893)
+ </para></listitem>
+
+ <listitem><para>
Failure of a <literal>BEFORE</literal> trigger did not prevent the
triggering statement from performing its operation on the row for
which the trigger error occurred. Now the triggering statement
@@ -1999,7 +2007,9 @@
<itemizedlist>
-<!-- Leave the security fix item as first in the list so it stands out better -->
+<!--
+ Leave the security fix item as first in the list so it stands out better
+-->
<listitem><para>
<emphasis role="bold">Security fix:</emphasis> If
--- 1.52/refman/news.xml 2005-07-11 16:05:14 +02:00
+++ 1.53/refman/news.xml 2005-07-12 00:31:36 +02:00
@@ -620,6 +620,50 @@
Thanks!
-->
+<!--
+ Leave the security fix item as first in the list so it stands out better
+-->
+
+ <listitem><para>
+ <emphasis role="bold">Security fix</emphasis>: On Windows systems,
+ a user with any of the following privileges
+
+ <itemizedlist>
+
+ <listitem><para>
+ <literal>REFERENCES</literal>
+ </para></listitem>
+
+ <listitem><para>
+ <literal>CREATE TEMPORARY TABLES</literal>
+ </para></listitem>
+
+ <listitem><para>
+ <literal>GRANT OPTION</literal>
+ </para></listitem>
+
+ <listitem><para>
+ <literal>CREATE</literal>
+ </para></listitem>
+
+ <listitem><para>
+ <literal>SELECT</literal>
+ </para></listitem>
+
+ </itemizedlist>
+
+ on <literal>*.*</literal> could crash <literal>mysqld</literal> by
+ issuing a <literal>USE LPT1;</literal> or <literal>USE
+ PRN;</literal> command. In addition, any of the commands
+ <literal>USE NUL;</literal>, <literal>USE CON;</literal>,
+ <literal>USE COM1;</literal>, or <literal>USE AUX;</literal> would
+ report success even though the database was not in fact changed.
+ <emphasis role="bold">Note</emphasis>: Although this bug was
+ thought to be fixed previously, it was later discovered to be
+ present in the MySQL 5.0.7-beta release for Windows. (Bug #9148,
+ <ulink url="http://cve.mitre.org/cvename.cgi?name=CAN-2005-0799">CAN-2005-0799</ulink>
+ </para></listitem>
+
<listitem><para>
<literal>mysqld_safe</literal> would sometimes fail to remove the
pid file for the old <literal>mysql</literal> process after a
@@ -693,46 +737,6 @@
</para></listitem>
<listitem><para>
- <emphasis role="bold">Security fix</emphasis>: On Windows systems,
- a user with any of the following privileges
-
- <itemizedlist>
-
- <listitem><para>
- <literal>REFERENCES</literal>
- </para></listitem>
-
- <listitem><para>
- <literal>CREATE TEMPORARY TABLES</literal>
- </para></listitem>
-
- <listitem><para>
- <literal>GRANT OPTION</literal>
- </para></listitem>
-
- <listitem><para>
- <literal>CREATE</literal>
- </para></listitem>
-
- <listitem><para>
- <literal>SELECT</literal>
- </para></listitem>
-
- </itemizedlist>
-
- on <literal>*.*</literal> could crash <literal>mysqld</literal> by
- issuing a <literal>USE LPT1;</literal> or <literal>USE
- PRN;</literal> command. In addition, any of the commands
- <literal>USE NUL;</literal>, <literal>USE CON;</literal>,
- <literal>USE COM1;</literal>, or <literal>USE AUX;</literal> would
- report success even though the database was not in fact changed.
- <emphasis role="bold">Note</emphasis>: Although this bug was
- thought to be fixed previously, it was later discovered to be
- present in the MySQL 5.0.7-beta release for Windows. (Bug #9148,
- <ulink url="http://cve.mitre.org/cvename.cgi?name=CAN-2005-0799">CAN-2005-0799</ulink>
- </para></listitem>
-
- <listitem><para>
An issue with index merging could cause suboptimal index merge
plans to be chosen when searching by indexes created on
<literal>DATE</literal> columns. The same issue caused the InnoDB
@@ -1091,9 +1095,9 @@
<itemizedlist>
- <listitem><para>
- Triggers with dropped functions caused crashes. (Bug #5893)
- </para></listitem>
+<!--
+ Leave the security fix item as first in the list so it stands out better
+-->
<listitem><para>
<emphasis role="bold">Security update</emphasis>: A user with
@@ -1104,6 +1108,10 @@
</para></listitem>
<listitem><para>
+ Triggers with dropped functions caused crashes. (Bug #5893)
+ </para></listitem>
+
+ <listitem><para>
Failure of a <literal>BEFORE</literal> trigger did not prevent the
triggering statement from performing its operation on the row for
which the trigger error occurred. Now the triggering statement
@@ -1989,7 +1997,9 @@
<itemizedlist>
-<!-- Leave the security fix item as first in the list so it stands out better -->
+<!--
+ Leave the security fix item as first in the list so it stands out better
+-->
<listitem><para>
<emphasis role="bold">Security fix:</emphasis> If
| Thread |
|---|
| • bk commit - mysqldoc@docsrva tree (stefan:1.2993) | stefan | 12 Jul |
