bk commit - mysqldoc@docsrva tree (paul:1.3003)

[paul]

Below is the list of changes that have just been committed into a local
mysqldoc repository of paul. When paul 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.3003 05/07/12 14:58:54 paul@stripped +3 -0
  Tweak.

  refman/news.xml
    1.60 05/07/12 14:58:53 paul@stripped +4 -2
    Tweak.

  refman-5.0/news.xml
    1.52 05/07/12 14:58:52 paul@stripped +45 -21
    Sync.

  refman-4.1/news.xml
    1.43 05/07/12 14:58:52 paul@stripped +8 -1
    Sync.

# 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:	paul
# Host:	kite-hub.kitebird.com
# Root:	/src/extern/MySQL/bk/mysqldoc

--- 1.42/refman-4.1/news.xml	2005-07-12 14:16:03 -05:00
+++ 1.43/refman-4.1/news.xml	2005-07-12 14:58:52 -05:00
@@ -257,6 +257,12 @@
      describe the  issue that was fixed. Use past tense. -->
 
     <listitem><para>
+     Selecting the result of an aggregate function for an
+     <literal>ENUM</literal> or <literal>SET</literal> column
within a
+     subquery could result in a server crash. (Bug #11821)
+    </para></listitem>
+
+    <listitem><para>
      When used in joins, <literal>SUBSTRING()</literal> failed to
      truncate to zero those string values that could not be converted to
      numbers. (Bug #10124)
@@ -350,7 +356,8 @@
     </para></listitem>
 
     <listitem><para>
-     Cluster failed to build with GCC 4.0. (Bug #11377)
+     Cluster failed to build with <command>gcc</command> 4.0. (Bug
+     #11377)
     </para></listitem>
 
     <listitem><para>

--- 1.51/refman-5.0/news.xml	2005-07-12 14:16:03 -05:00
+++ 1.52/refman-5.0/news.xml	2005-07-12 14:58:52 -05:00
@@ -221,6 +221,44 @@
    <itemizedlist>
 
     <listitem><para>
+     It is no longer necessary to issue an explicit <literal>LOCK
+     TABLES</literal> for any tables accessed by a trigger prior to
+     executing any statements that might invoke the trigger. (Bug #9581,
+     Bug #8406)
+    </para></listitem>
+
+   </itemizedlist>
+
+   <para>
+    Bugs fixed:
+   </para>
+
+   <itemizedlist>
+
+    <listitem><para>
+     Selecting the result of an aggregate function for an
+     <literal>ENUM</literal> or <literal>SET</literal> column
within a
+     subquery could result in a server crash. (Bug #11821)
+    </para></listitem>
+
+    <listitem><para>
+     Incorrect column values could be retrieved from views defined using
+     statements of the form <literal>SELECT * FROM
+     <replaceable>tbl_name</replaceable></literal>. (Bug #11771)
+    </para></listitem>
+
+    <listitem><para>
+     The <literal>mysql.proc</literal> table was not being created
+     properly with the proper <literal>utf8</literal> character set and
+     collation, causing server crashes for stored procedure operations
+     if the server was using a multi-byte character set. To take
+     advantage of the bug fix,
+     <command>mysql_fix_privileges_tables</command> should be run to
+     correct the structure of the <literal>mysql.proc</literal> table.
+     (Bug #11365)
+    </para></listitem>
+
+    <listitem><para>
      Execution of a prepared statement that invoked a non-existent or
      dropped stored routine would crash the server. (Bug #11834)
     </para></listitem>
@@ -243,21 +281,6 @@
     </para></listitem>
 
     <listitem><para>
-     It is no longer necessary to issue an explicit <literal>LOCK
-     TABLES</literal> for any tables accessed by a trigger prior to
-     executing any statements that might invoke the trigger. (Bug #9581,
-     Bug #8406)
-    </para></listitem>
-
-   </itemizedlist>
-
-   <para>
-    Bugs fixed:
-   </para>
-
-   <itemizedlist>
-
-    <listitem><para>
      In a shared Windows environment, MySQL could not find its
      configuration file unless the file was in the
      <filename>C:\</filename> directory. (Bug #5354)
@@ -290,7 +313,8 @@
     <listitem><para>
      <literal>InnoDB</literal>: Various optimizations. Removed
      unreachable debug code from non-debug builds. Added hints for the
-     branch predictor in GCC. Made assertions occupy less space.
+     branch predictor in <command>gcc</command>. Made assertions occupy
+     less space.
     </para></listitem>
 
     <listitem><para>
@@ -378,16 +402,16 @@
     </para></listitem>
 
     <listitem><para>
+     Running a <literal>CHECK TABLES</literal> on multiple views crashed
+     the server. (Bug #11337)
+    </para></listitem>
+
+    <listitem><para>
      When a table had a primary key containing a <literal>BLOB</literal>
      column, creation of another index failed with the error
      <literal>BLOB/TEXT column used in key specification without
      keylength</literal>, even when the new index did not contain a
      <literal>BLOB</literal> column. (Bug #11657)
-    </para></listitem>
-
-    <listitem><para>
-     Running a <literal>CHECK TABLES</literal> on multiple views crashed
-     the server. (Bug #11337)
     </para></listitem>
 
     <listitem><para>

--- 1.59/refman/news.xml	2005-07-12 14:42:57 -05:00
+++ 1.60/refman/news.xml	2005-07-12 14:58:53 -05:00
@@ -309,7 +309,8 @@
     <listitem><para>
      <literal>InnoDB</literal>: Various optimizations. Removed
      unreachable debug code from non-debug builds. Added hints for the
-     branch predictor in GCC. Made assertions occupy less space.
+     branch predictor in <command>gcc</command>. Made assertions occupy
+     less space.
     </para></listitem>
 
     <listitem><para>
@@ -5070,7 +5071,8 @@
     </para></listitem>
 
     <listitem><para>
-     Cluster failed to build with GCC 4.0. (Bug #11377)
+     Cluster failed to build with <command>gcc</command> 4.0. (Bug
+     #11377)
     </para></listitem>
 
     <listitem><para>