Author: jstephens
Date: 2006-08-09 15:47:16 +0200 (Wed, 09 Aug 2006)
New Revision: 2980
Log:
Documenting bugfixes:
Bug #17647, Bug #7498, Bug #10979, Bug #16881, Bug #21091
Modified:
trunk/refman-4.1/database-administration.xml
trunk/refman-5.0/database-administration.xml
trunk/refman-5.1/database-administration.xml
trunk/refman-common/news-4.1.xml
trunk/refman-common/news-5.0.xml
trunk/refman-common/news-5.1.xml
Modified: trunk/refman-4.1/database-administration.xml
===================================================================
--- trunk/refman-4.1/database-administration.xml 2006-08-08 17:54:31 UTC (rev 2979)
+++ trunk/refman-4.1/database-administration.xml 2006-08-09 13:47:16 UTC (rev 2980)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 0; 801 bytes
@@ -15080,6 +15080,13 @@
<literal>USE <replaceable>db_name</replaceable></literal>
statement.
</para>
+
+ <para>
+ <emphasis role="bold">Note</emphasis>: Client applications
+ may cache the database name; thus, this effect may not be
+ visible to them without actually changing to a different database or
+ executing a <literal>FLUSH PRIVILEGES</literal> statement.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-5.0/database-administration.xml
===================================================================
--- trunk/refman-5.0/database-administration.xml 2006-08-08 17:54:31 UTC (rev 2979)
+++ trunk/refman-5.0/database-administration.xml 2006-08-09 13:47:16 UTC (rev 2980)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 0; 801 bytes
@@ -18023,6 +18023,13 @@
<literal>USE <replaceable>db_name</replaceable></literal>
statement.
</para>
+
+ <para>
+ <emphasis role="bold">Note</emphasis>: Client applications
+ may cache the database name; thus, this effect may not be
+ visible to them without actually changing to a different database or
+ executing a <literal>FLUSH PRIVILEGES</literal> statement.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-5.1/database-administration.xml
===================================================================
--- trunk/refman-5.1/database-administration.xml 2006-08-08 17:54:31 UTC (rev 2979)
+++ trunk/refman-5.1/database-administration.xml 2006-08-09 13:47:16 UTC (rev 2980)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 0; 801 bytes
@@ -18122,6 +18122,13 @@
<literal>USE <replaceable>db_name</replaceable></literal>
statement.
</para>
+
+ <para>
+ <emphasis role="bold">Note</emphasis>: Client applications
+ may cache the database name; thus, this effect may not be
+ visible to them without actually changing to a different database or
+ executing a <literal>FLUSH PRIVILEGES</literal> statement.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml 2006-08-08 17:54:31 UTC (rev 2979)
+++ trunk/refman-common/news-4.1.xml 2006-08-09 13:47:16 UTC (rev 2980)
Changed blocks: 2, Lines Added: 23, Lines Deleted: 0; 1417 bytes
@@ -190,6 +190,19 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ A query using <literal>WHERE <replaceable>column</replaceable>
+ = <replaceable>constant</replaceable> OR
+ <replaceable>column</replaceable> IS NULL</literal> did not
+ return consistent results on successive invocations. The
+ <replaceable>column</replaceable> in each part of the
+ <literal>WHERE</literal> clause could be either the same
+ column, or two different columns, for the effect to be
+ observed. (Bug #21091)
+ </para>
+ </listitem>
<listitem>
<para>
@@ -393,6 +406,16 @@
</remark>
<itemizedlist>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Security fix</emphasis>: On Linux, and
+ possibly other platforms using case-sensitive filesystems, it
+ was possible for a user granted rights on a database to create
+ or access a database whose name differed only from that of the
+ first by the case of one or more letters. (Bug #17647)
+ </para>
+ </listitem>
<listitem>
<para>
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2006-08-08 17:54:31 UTC (rev 2979)
+++ trunk/refman-common/news-5.0.xml 2006-08-09 13:47:16 UTC (rev 2980)
Changed blocks: 2, Lines Added: 45, Lines Deleted: 0; 2141 bytes
@@ -304,6 +304,44 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Security fix</emphasis>: On Linux, and
+ possibly other platforms using case-sensitive filesystems, it
+ was possible for a user granted rights on a database to create
+ or access a database whose name differed only from that of the
+ first by the case of one or more letters. (Bug #17647)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A query using <literal>WHERE <replaceable>column</replaceable>
+ = <replaceable>constant</replaceable> OR
+ <replaceable>column</replaceable> IS NULL</literal> did not
+ return consistent results on successive invocations. The
+ <replaceable>column</replaceable> in each part of the
+ <literal>WHERE</literal> clause could be either the same
+ column, or two different columns, for the effect to be
+ observed. (Bug #21091)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>PASSWORD()</literal> function returned invalid
+ results when used in some <literal>UNION</literal> queries.
+ (bug #16881)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>USE</literal> did not refresh database privileges
+ when employed to re-select the current database. (Bug #10979)
+ </para>
+ </listitem>
<listitem>
<para>
@@ -317,6 +355,13 @@
(<replaceable>subquery</replaceable>))</literal>. (Bug #20975)
</para>
</listitem>
+
+ <listitem>
+ <para>
+ A user variable set to a value selected from an unsigned
+ column was stored as a signed value. (Bug #7498)
+ </para>
+ </listitem>
<listitem>
<para>
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-08-08 17:54:31 UTC (rev 2979)
+++ trunk/refman-common/news-5.1.xml 2006-08-09 13:47:16 UTC (rev 2980)
Changed blocks: 2, Lines Added: 30, Lines Deleted: 0; 1698 bytes
@@ -412,6 +412,16 @@
</remark>
<itemizedlist>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Security fix</emphasis>: On Linux, and
+ possibly other platforms using case-sensitive filesystems, it
+ was possible for a user granted rights on a database to create
+ or access a database whose name differed only from that of the
+ first by the case of one or more letters. (Bug #17647)
+ </para>
+ </listitem>
<listitem>
<para>
@@ -458,6 +468,26 @@
conditions so as to be more informative. (Bug #10946)
</para>
</listitem>
+
+ <listitem>
+ <para>
+ A query using <literal>WHERE <replaceable>column</replaceable>
+ = <replaceable>constant</replaceable> OR
+ <replaceable>column</replaceable> IS NULL</literal> did not
+ return consistent results on successive invocations. The
+ <replaceable>column</replaceable> in each part of the
+ <literal>WHERE</literal> clause could be either the same
+ column, or two different columns, for the effect to be
+ observed. (Bug #21091)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>USE</literal> did not refresh database privileges
+ when employed to re-select the current database. (Bug #10979)
+ </para>
+ </listitem>
<listitem>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r2980 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-common | jon | 9 Aug |
