Below is the list of changes that have just been committed into a local
mysqldoc repository of jon. When jon 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.2869 05/06/24 14:28:29 jon@stripped +3 -0
Documented bugfixes:
Bug#9998
Bug#10964
Bug#10732
Bug#10543
Sync refman-4.1 and refman-5.0 to refman tree.
refman/news.xml
1.28 05/06/24 14:28:27 jon@stripped +132 -58
Documented bugfixes:
Bug#9998
Bug#10964
Bug#10732
Bug#10543
refman-5.0/news.xml
1.23 05/06/24 14:28:26 jon@stripped +163 -64
sync to refman
refman-4.1/news.xml
1.23 05/06/24 14:28:26 jon@stripped +163 -64
sync to refman
# 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: jon
# Host: gigan.site
# Root: /home/jon/bk/mysqldoc
--- 1.22/refman-4.1/news.xml 2005-06-24 08:01:05 +10:00
+++ 1.23/refman-4.1/news.xml 2005-06-24 14:28:26 +10:00
@@ -334,64 +334,115 @@
</listitem>
-->
- <listitem><para>
- <literal>sql_data_access</literal> column of
- <literal>routines</literal> table of
- <literal>INFORMATION_SCHEMA</literal> was empty. (Bug #11055)
- </para></listitem>
-
- <listitem><para>
- A <literal>CAST()</literal> value could not be included in a
- <literal>VIEW</literal>. (Bug #11387)
- </para></listitem>
+<!--
+ NOTE:
- <listitem><para>
- Server crashed when using <literal>GROUP BY</literal> on the result
- of a <literal>DIV</literal> operation on a
- <literal>DATETIME</literal> value. (Bug #11385)
- </para></listitem>
+ Please format code so that opening and closing
+ <listitem>...</listitem> tags are on separate lines from the listitem
+ content. This makes it *much* easier to navigate the XML code and to
+ spot problems when using a text editor that has code-folding. E.g.,
- <listitem><para>
- Possible <literal>NULL</literal> values in <literal>BLOB</literal>
- columns could crash server when <literal>BLOB</literal> used in
- <literal>GROUP BY</literal>. (Bug #11295)
- </para></listitem>
+ <listitem>
+ <para>blah</para>
+<programlisting>
+</programlisting>
+ <para>blah</para>
+ <para>blah</para>
+ [etc. ...]
+ </listem>
+
+ Grouping the opening <listitem><para> together on a single line means
+ that you can't open/close the para element separately from the
+ listitem using a "tree" view of the doc, which is quite annoying.
+
+ If you're using xmlformat or some other tool that reformats
+ automatically, either run it with options that *don't* place
+ <listitem> and following tags together on the same line, or use
+ "make manual.valid" instead.
+
+ Also remember that our guidelines call for *two* spaces in lieu of
+ tabs; this should be adhered to no matter what language the code is
+ written in. If your editor is doing something else, then your editor
+ is incorrectly configured and needs to be fixed.
- <listitem><para>
- Fixed 64 bit compiler warning for packet length in replication.
- (Bug #11064)
- </para></listitem>
+ Thanks!
+-->
- <listitem><para>
- Multiple range accesses in a subquery cause server crash. (Bug
- #11487)
- </para></listitem>
-
- <listitem><para>
- <emphasis role="bold">Security fix</emphasis>: On Windows systems,
- a user with any of the following privileges
+ <listitem>
+ <para>Converting a <literal>VARCHAR</literal> column having an
+ index to a different type (such as <literal>TINYTEXT</literal>)
+ gave rise to an incorrect error message. (Bug #10543)</para>
+
+ <para>Note that this bugfix induces a slight change in the
+ behaviour of indexes: If an index is defined to be the same length
+ as a field (or is left to default to that field's length), and the
+ length of the field is later changed, then the index will adopt
+ the new length of the field. Previously, the size of the index did
+ not change for some field types (such as
+ <literal>VARCHAR</literal>) when the field type was
+ changed.</para>
+ </listitem>
+
+ <listitem>
+ <para><literal>sql_data_access</literal> column of
+ <literal>routines</literal> table of
+ <literal>INFORMATION_SCHEMA</literal> was empty.
+ (Bug #11055)</para>
+ </listitem>
+
+ <listitem>
+ <para>A <literal>CAST()</literal> value could not be included in a
+ <literal>VIEW</literal>. (Bug #11387)</para>
+ </listitem>
+
+ <listitem>
+ <para>Server crashed when using <literal>GROUP BY</literal> on the
+ result of a <literal>DIV</literal> operation on a
+ <literal>DATETIME</literal> value. (Bug #11385)</para>
+ </listitem>
+
+ <listitem>
+ <para>Possible <literal>NULL</literal> values in
+ <literal>BLOB</literal> columns could crash the server when
+ a <literal>BLOB</literal> was used in a
+ <literal>GROUP BY</literal> query. (Bug #11295)</para>
+ </listitem>
+
+ <listitem>
+ <para>Fixed 64 bit compiler warning for packet length in
+ replication. (Bug #11064)</para>
+ </listitem>
+
+ <listitem>
+ <para>Multiple range accesses in a subquery cause server crash.
+ (Bug #11487)</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>
+ <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>
@@ -407,13 +458,13 @@
<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
- storage engine to issue the warning <literal>using a partial-field
- key prefix in search</literal>. (Bug #8441)
- </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
+ storage engine to issue the warning <literal>using a partial-field
+ key prefix in search</literal>. (Bug #8441)</para>
+ </listitem>
<listitem><para>
The <literal>mysqlhotcopy</literal> script was not parsing the
@@ -448,9 +499,10 @@
</para></listitem>
<listitem><para>
- Fixed hang/crash with Boolean full-text search against an unindexed
- field for which the query contained more words than we allocated
- space. (Bug #7858)
+ Fixed hang/crash with Boolean full-text search where a query
+ contained more query terms that one-third of the query length (it
+ could be achieved with truncation operator: 'a*b*c*d*'). (Bug
+ #7858)
</para></listitem>
<listitem><para>
@@ -703,6 +755,24 @@
prepared statements. (Bug #7306)
</para></listitem>
+ <listitem>
+ <para><emphasis role="bold">Security update</emphasis>: A user
+ with limited privileges could obtain information about the
+ privileges of other users by querying objects in the
+ <literal>INFORMATION_SCHEMA</literal> database for which that user
+ did not have the requisite privileges. (Bug #10964)</para>
+ </listitem>
+
+ <listitem>
+ <para>Issuing a write lock for a table from one client prevented
+ other clients from accessing the table's metadata. For example, if
+ one client issued a <literal>LOCK TABLES
+ <replaceable>mydb</replaceable>.<replaceable>mytable</replaceable>
+ WRITE</literal>, then a second client attempting to execute a
+ <literal>USE <replaceable>mydb</replaceable>;</literal> would
+ hang. (Bug #9998)</para>
+ </listitem>
+
<listitem><para>
<literal>SHOW BINARY LOGS</literal> now displays a
<literal>File_size</literal> column that indicates the size of each
@@ -756,6 +826,24 @@
<itemizedlist>
+ <listitem>
+ <para><emphasis role="bold">Security update</emphasis>: A user
+ with limited privileges could obtain information about the
+ privileges of other users by querying objects in the
+ <literal>INFORMATION_SCHEMA</literal> database for which that user
+ did not have the requisite privileges. (Bug #10964)</para>
+ </listitem>
+
+ <listitem>
+ <para>Issuing a write lock for a table from one client prevented
+ other clients from accessing the table's metadata. For example, if
+ one client issued a <literal>LOCK TABLES
+ <replaceable>mydb</replaceable>.<replaceable>mytable</replaceable>
+ WRITE</literal>, then a second client attempting to execute a
+ <literal>USE <replaceable>mydb</replaceable>;</literal> would
+ hang. (Bug #9998)</para>
+ </listitem>
+
<listitem><para>
The <literal>LAST_DAY()</literal> failed to return
<literal>NULL</literal> when supplied with an invalid argument. See
@@ -4514,6 +4602,16 @@
<!-- NOTE: No need to start every item with "Fixed..."; sufficient to
describe the issue that was fixed. Use past tense. -->
+ <listitem>
+ <para>Setting <literal>@@SQL_MODE = NULL</literal> caused an
+ erroneous error message. (Bug #10732)</para>
+ </listitem>
+
+ <listitem>
+ <para>Setting <literal>@@SQL_MODE = NULL</literal> caused an
+ erroneous error message. (Bug #10732)</para>
+ </listitem>
+
<listitem><para>
Server crashed when using <literal>GROUP BY</literal> on the result
of a <literal>DIV</literal> operation on a
@@ -4650,9 +4748,10 @@
</para></listitem>
<listitem><para>
- Fixed hang/crash with Boolean full-text search against an unindexed
- field for which the query contained more words than we allocated
- space. (Bug #7858)
+ Fixed hang/crash with Boolean full-text search where a query
+ contained more query terms that one-third of the query length (it
+ could be achieved with truncation operator: 'a*b*c*d*'). (Bug
+ #7858)
</para></listitem>
<listitem><para>
--- 1.22/refman-5.0/news.xml 2005-06-24 08:01:06 +10:00
+++ 1.23/refman-5.0/news.xml 2005-06-24 14:28:26 +10:00
@@ -334,64 +334,115 @@
</listitem>
-->
- <listitem><para>
- <literal>sql_data_access</literal> column of
- <literal>routines</literal> table of
- <literal>INFORMATION_SCHEMA</literal> was empty. (Bug #11055)
- </para></listitem>
-
- <listitem><para>
- A <literal>CAST()</literal> value could not be included in a
- <literal>VIEW</literal>. (Bug #11387)
- </para></listitem>
+<!--
+ NOTE:
- <listitem><para>
- Server crashed when using <literal>GROUP BY</literal> on the result
- of a <literal>DIV</literal> operation on a
- <literal>DATETIME</literal> value. (Bug #11385)
- </para></listitem>
+ Please format code so that opening and closing
+ <listitem>...</listitem> tags are on separate lines from the listitem
+ content. This makes it *much* easier to navigate the XML code and to
+ spot problems when using a text editor that has code-folding. E.g.,
- <listitem><para>
- Possible <literal>NULL</literal> values in <literal>BLOB</literal>
- columns could crash server when <literal>BLOB</literal> used in
- <literal>GROUP BY</literal>. (Bug #11295)
- </para></listitem>
+ <listitem>
+ <para>blah</para>
+<programlisting>
+</programlisting>
+ <para>blah</para>
+ <para>blah</para>
+ [etc. ...]
+ </listem>
+
+ Grouping the opening <listitem><para> together on a single line means
+ that you can't open/close the para element separately from the
+ listitem using a "tree" view of the doc, which is quite annoying.
+
+ If you're using xmlformat or some other tool that reformats
+ automatically, either run it with options that *don't* place
+ <listitem> and following tags together on the same line, or use
+ "make manual.valid" instead.
+
+ Also remember that our guidelines call for *two* spaces in lieu of
+ tabs; this should be adhered to no matter what language the code is
+ written in. If your editor is doing something else, then your editor
+ is incorrectly configured and needs to be fixed.
- <listitem><para>
- Fixed 64 bit compiler warning for packet length in replication.
- (Bug #11064)
- </para></listitem>
+ Thanks!
+-->
- <listitem><para>
- Multiple range accesses in a subquery cause server crash. (Bug
- #11487)
- </para></listitem>
-
- <listitem><para>
- <emphasis role="bold">Security fix</emphasis>: On Windows systems,
- a user with any of the following privileges
+ <listitem>
+ <para>Converting a <literal>VARCHAR</literal> column having an
+ index to a different type (such as <literal>TINYTEXT</literal>)
+ gave rise to an incorrect error message. (Bug #10543)</para>
+
+ <para>Note that this bugfix induces a slight change in the
+ behaviour of indexes: If an index is defined to be the same length
+ as a field (or is left to default to that field's length), and the
+ length of the field is later changed, then the index will adopt
+ the new length of the field. Previously, the size of the index did
+ not change for some field types (such as
+ <literal>VARCHAR</literal>) when the field type was
+ changed.</para>
+ </listitem>
+
+ <listitem>
+ <para><literal>sql_data_access</literal> column of
+ <literal>routines</literal> table of
+ <literal>INFORMATION_SCHEMA</literal> was empty.
+ (Bug #11055)</para>
+ </listitem>
+
+ <listitem>
+ <para>A <literal>CAST()</literal> value could not be included in a
+ <literal>VIEW</literal>. (Bug #11387)</para>
+ </listitem>
+
+ <listitem>
+ <para>Server crashed when using <literal>GROUP BY</literal> on the
+ result of a <literal>DIV</literal> operation on a
+ <literal>DATETIME</literal> value. (Bug #11385)</para>
+ </listitem>
+
+ <listitem>
+ <para>Possible <literal>NULL</literal> values in
+ <literal>BLOB</literal> columns could crash the server when
+ a <literal>BLOB</literal> was used in a
+ <literal>GROUP BY</literal> query. (Bug #11295)</para>
+ </listitem>
+
+ <listitem>
+ <para>Fixed 64 bit compiler warning for packet length in
+ replication. (Bug #11064)</para>
+ </listitem>
+
+ <listitem>
+ <para>Multiple range accesses in a subquery cause server crash.
+ (Bug #11487)</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>
+ <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>
@@ -407,13 +458,13 @@
<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
- storage engine to issue the warning <literal>using a partial-field
- key prefix in search</literal>. (Bug #8441)
- </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
+ storage engine to issue the warning <literal>using a partial-field
+ key prefix in search</literal>. (Bug #8441)</para>
+ </listitem>
<listitem><para>
The <literal>mysqlhotcopy</literal> script was not parsing the
@@ -448,9 +499,10 @@
</para></listitem>
<listitem><para>
- Fixed hang/crash with Boolean full-text search against an unindexed
- field for which the query contained more words than we allocated
- space. (Bug #7858)
+ Fixed hang/crash with Boolean full-text search where a query
+ contained more query terms that one-third of the query length (it
+ could be achieved with truncation operator: 'a*b*c*d*'). (Bug
+ #7858)
</para></listitem>
<listitem><para>
@@ -703,6 +755,24 @@
prepared statements. (Bug #7306)
</para></listitem>
+ <listitem>
+ <para><emphasis role="bold">Security update</emphasis>: A user
+ with limited privileges could obtain information about the
+ privileges of other users by querying objects in the
+ <literal>INFORMATION_SCHEMA</literal> database for which that user
+ did not have the requisite privileges. (Bug #10964)</para>
+ </listitem>
+
+ <listitem>
+ <para>Issuing a write lock for a table from one client prevented
+ other clients from accessing the table's metadata. For example, if
+ one client issued a <literal>LOCK TABLES
+ <replaceable>mydb</replaceable>.<replaceable>mytable</replaceable>
+ WRITE</literal>, then a second client attempting to execute a
+ <literal>USE <replaceable>mydb</replaceable>;</literal> would
+ hang. (Bug #9998)</para>
+ </listitem>
+
<listitem><para>
<literal>SHOW BINARY LOGS</literal> now displays a
<literal>File_size</literal> column that indicates the size of each
@@ -756,6 +826,24 @@
<itemizedlist>
+ <listitem>
+ <para><emphasis role="bold">Security update</emphasis>: A user
+ with limited privileges could obtain information about the
+ privileges of other users by querying objects in the
+ <literal>INFORMATION_SCHEMA</literal> database for which that user
+ did not have the requisite privileges. (Bug #10964)</para>
+ </listitem>
+
+ <listitem>
+ <para>Issuing a write lock for a table from one client prevented
+ other clients from accessing the table's metadata. For example, if
+ one client issued a <literal>LOCK TABLES
+ <replaceable>mydb</replaceable>.<replaceable>mytable</replaceable>
+ WRITE</literal>, then a second client attempting to execute a
+ <literal>USE <replaceable>mydb</replaceable>;</literal> would
+ hang. (Bug #9998)</para>
+ </listitem>
+
<listitem><para>
The <literal>LAST_DAY()</literal> failed to return
<literal>NULL</literal> when supplied with an invalid argument. See
@@ -4514,6 +4602,16 @@
<!-- NOTE: No need to start every item with "Fixed..."; sufficient to
describe the issue that was fixed. Use past tense. -->
+ <listitem>
+ <para>Setting <literal>@@SQL_MODE = NULL</literal> caused an
+ erroneous error message. (Bug #10732)</para>
+ </listitem>
+
+ <listitem>
+ <para>Setting <literal>@@SQL_MODE = NULL</literal> caused an
+ erroneous error message. (Bug #10732)</para>
+ </listitem>
+
<listitem><para>
Server crashed when using <literal>GROUP BY</literal> on the result
of a <literal>DIV</literal> operation on a
@@ -4650,9 +4748,10 @@
</para></listitem>
<listitem><para>
- Fixed hang/crash with Boolean full-text search against an unindexed
- field for which the query contained more words than we allocated
- space. (Bug #7858)
+ Fixed hang/crash with Boolean full-text search where a query
+ contained more query terms that one-third of the query length (it
+ could be achieved with truncation operator: 'a*b*c*d*'). (Bug
+ #7858)
</para></listitem>
<listitem><para>
--- 1.27/refman/news.xml 2005-06-24 08:07:47 +10:00
+++ 1.28/refman/news.xml 2005-06-24 14:28:27 +10:00
@@ -334,64 +334,115 @@
</listitem>
-->
- <listitem><para>
- <literal>sql_data_access</literal> column of
- <literal>routines</literal> table of
- <literal>INFORMATION_SCHEMA</literal> was empty. (Bug #11055)
- </para></listitem>
-
- <listitem><para>
- A <literal>CAST()</literal> value could not be included in a
- <literal>VIEW</literal>. (Bug #11387)
- </para></listitem>
-
- <listitem><para>
- Server crashed when using <literal>GROUP BY</literal> on the result
- of a <literal>DIV</literal> operation on a
- <literal>DATETIME</literal> value. (Bug #11385)
- </para></listitem>
+<!--
+ NOTE:
- <listitem><para>
- Possible <literal>NULL</literal> values in <literal>BLOB</literal>
- columns could crash server when <literal>BLOB</literal> used in
- <literal>GROUP BY</literal>. (Bug #11295)
- </para></listitem>
+ Please format code so that opening and closing
+ <listitem>...</listitem> tags are on separate lines from the listitem
+ content. This makes it *much* easier to navigate the XML code and to
+ spot problems when using a text editor that has code-folding. E.g.,
- <listitem><para>
- Fixed 64 bit compiler warning for packet length in replication.
- (Bug #11064)
- </para></listitem>
+ <listitem>
+ <para>blah</para>
+<programlisting>
+</programlisting>
+ <para>blah</para>
+ <para>blah</para>
+ [etc. ...]
+ </listem>
+
+ Grouping the opening <listitem><para> together on a single line means
+ that you can't open/close the para element separately from the
+ listitem using a "tree" view of the doc, which is quite annoying.
+
+ If you're using xmlformat or some other tool that reformats
+ automatically, either run it with options that *don't* place
+ <listitem> and following tags together on the same line, or use
+ "make manual.valid" instead.
+
+ Also remember that our guidelines call for *two* spaces in lieu of
+ tabs; this should be adhered to no matter what language the code is
+ written in. If your editor is doing something else, then your editor
+ is incorrectly configured and needs to be fixed.
- <listitem><para>
- Multiple range accesses in a subquery cause server crash. (Bug
- #11487)
- </para></listitem>
+ Thanks!
+-->
- <listitem><para>
- <emphasis role="bold">Security fix</emphasis>: On Windows systems,
- a user with any of the following privileges
+ <listitem>
+ <para>Converting a <literal>VARCHAR</literal> column having an
+ index to a different type (such as <literal>TINYTEXT</literal>)
+ gave rise to an incorrect error message. (Bug #10543)</para>
+
+ <para>Note that this bugfix induces a slight change in the
+ behaviour of indexes: If an index is defined to be the same length
+ as a field (or is left to default to that field's length), and the
+ length of the field is later changed, then the index will adopt
+ the new length of the field. Previously, the size of the index did
+ not change for some field types (such as
+ <literal>VARCHAR</literal>) when the field type was
+ changed.</para>
+ </listitem>
+
+ <listitem>
+ <para><literal>sql_data_access</literal> column of
+ <literal>routines</literal> table of
+ <literal>INFORMATION_SCHEMA</literal> was empty.
+ (Bug #11055)</para>
+ </listitem>
+
+ <listitem>
+ <para>A <literal>CAST()</literal> value could not be included in a
+ <literal>VIEW</literal>. (Bug #11387)</para>
+ </listitem>
+
+ <listitem>
+ <para>Server crashed when using <literal>GROUP BY</literal> on the
+ result of a <literal>DIV</literal> operation on a
+ <literal>DATETIME</literal> value. (Bug #11385)</para>
+ </listitem>
+
+ <listitem>
+ <para>Possible <literal>NULL</literal> values in
+ <literal>BLOB</literal> columns could crash the server when
+ a <literal>BLOB</literal> was used in a
+ <literal>GROUP BY</literal> query. (Bug #11295)</para>
+ </listitem>
+
+ <listitem>
+ <para>Fixed 64 bit compiler warning for packet length in
+ replication. (Bug #11064)</para>
+ </listitem>
+
+ <listitem>
+ <para>Multiple range accesses in a subquery cause server crash.
+ (Bug #11487)</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>
+ <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>
@@ -407,13 +458,13 @@
<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
- storage engine to issue the warning <literal>using a partial-field
- key prefix in search</literal>. (Bug #8441)
- </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
+ storage engine to issue the warning <literal>using a partial-field
+ key prefix in search</literal>. (Bug #8441)</para>
+ </listitem>
<listitem><para>
The <literal>mysqlhotcopy</literal> script was not parsing the
@@ -757,6 +808,24 @@
<itemizedlist>
+ <listitem>
+ <para><emphasis role="bold">Security update</emphasis>: A user
+ with limited privileges could obtain information about the
+ privileges of other users by querying objects in the
+ <literal>INFORMATION_SCHEMA</literal> database for which that user
+ did not have the requisite privileges. (Bug #10964)</para>
+ </listitem>
+
+ <listitem>
+ <para>Issuing a write lock for a table from one client prevented
+ other clients from accessing the table's metadata. For example, if
+ one client issued a <literal>LOCK TABLES
+ <replaceable>mydb</replaceable>.<replaceable>mytable</replaceable>
+ WRITE</literal>, then a second client attempting to execute a
+ <literal>USE <replaceable>mydb</replaceable>;</literal> would
+ hang. (Bug #9998)</para>
+ </listitem>
+
<listitem><para>
The <literal>LAST_DAY()</literal> failed to return
<literal>NULL</literal> when supplied with an invalid argument. See
@@ -4514,6 +4583,11 @@
<!-- NOTE: No need to start every item with "Fixed..."; sufficient to
describe the issue that was fixed. Use past tense. -->
+
+ <listitem>
+ <para>Setting <literal>@@SQL_MODE = NULL</literal> caused an
+ erroneous error message. (Bug #10732)</para>
+ </listitem>
<listitem><para>
Server crashed when using <literal>GROUP BY</literal> on the result
| Thread |
|---|
| • bk commit - mysqldoc@docsrva tree (jon:1.2869) | jon | 24 Jun |
