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

[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.3055 05/07/18 15:26:35 paul@stripped +3 -0
  Document bugfix. (Bug #9442)
  Document bugfix. (Bug #9565)
  Document bugfix. (Bug #9854)
  Document bugfix. (Bug #12004)

  refman/news.xml
    1.79 05/07/18 15:26:34 paul@stripped +56 -15
    Document bugfix. (Bug #9442)
    Document bugfix. (Bug #9565)
    Document bugfix. (Bug #9854)
    Document bugfix. (Bug #12004)

  refman-5.0/news.xml
    1.65 05/07/18 15:26:34 paul@stripped +33 -15
    Sync.

  refman-4.1/news.xml
    1.56 05/07/18 15:26:33 paul@stripped +17 -0
    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.55/refman-4.1/news.xml	2005-07-18 14:35:15 -05:00
+++ 1.56/refman-4.1/news.xml	2005-07-18 15:26:33 -05:00
@@ -195,6 +195,17 @@
    <itemizedlist>
 
     <listitem><para>
+     <literal>SHOW BINARY LOGS</literal> displayed a file size of 0 for
+     all log files but the current one if the files were not located in
+     the data directory. (Bug #12004)
+    </para></listitem>
+
+    <listitem><para>
+     Server-side prepared statements failed for columns with a character
+     set of <literal>ucs2</literal>. (Bug #9442)
+    </para></listitem>
+
+    <listitem><para>
      References to system variables in an SQL statement prepared with
      <literal>PREPARE</literal> were evaluated during
      <literal>EXECUTE</literal> to their values at prepare time, not to
@@ -340,6 +351,12 @@
 
 <!-- NOTE: No need to start every item with "Fixed..."; sufficient to
      describe the  issue that was fixed. Use past tense. -->
+
+    <listitem><para>
+     The handling by the <literal>HEX()</literal> function of numbers
+     larger than 2<superscript>64</superscript> was improved. (Bug
+     #9854)
+    </para></listitem>
 
     <listitem><para>
      Added a missing mutex when rotating the relay logs. Also, the

--- 1.64/refman-5.0/news.xml	2005-07-18 14:35:15 -05:00
+++ 1.65/refman-5.0/news.xml	2005-07-18 15:26:34 -05:00
@@ -237,6 +237,32 @@
     </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>
+     <literal>SHOW BINARY LOGS</literal> displayed a file size of 0 for
+     all log files but the current one if the files were not located in
+     the data directory. (Bug #12004)
+    </para></listitem>
+
+    <listitem><para>
+     Server-side prepared statements failed for columns with a character
+     set of <literal>ucs2</literal>. (Bug #9442)
+    </para></listitem>
+
+    <listitem><para>
      References to system variables in an SQL statement prepared with
      <literal>PREPARE</literal> were evaluated during
      <literal>EXECUTE</literal> to their values at prepare time, not to
@@ -266,25 +292,17 @@
     </para></listitem>
 
     <listitem><para>
-     Within a stored procedure, selecting from a table through a view
-     caused subsequent updates to the table to fail with a message that
-     the table was read-locked. (Bug #9597)
+     Within a stored procedure that selects from a table, invoking
+     another procedure that requires a write lock for the table caused
+     that procedure to fail with a message that the table was
+     read-locked. (Bug #9565)
     </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)
+     Within a stored procedure, selecting from a table through a view
+     caused subsequent updates to the table to fail with a message that
+     the table was read-locked. (Bug #9597)
     </para></listitem>
-
-   </itemizedlist>
-
-   <para>
-    Bugs fixed:
-   </para>
-
-   <itemizedlist>
 
     <listitem><para>
      For a stored procedure defined with <literal>SQL SECURITY

--- 1.78/refman/news.xml	2005-07-18 14:35:15 -05:00
+++ 1.79/refman/news.xml	2005-07-18 15:26:34 -05:00
@@ -229,6 +229,32 @@
     </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>
+     <literal>SHOW BINARY LOGS</literal> displayed a file size of 0 for
+     all log files but the current one if the files were not located in
+     the data directory. (Bug #12004)
+    </para></listitem>
+
+    <listitem><para>
+     Server-side prepared statements failed for columns with a character
+     set of <literal>ucs2</literal>. (Bug #9442)
+    </para></listitem>
+
+    <listitem><para>
      References to system variables in an SQL statement prepared with
      <literal>PREPARE</literal> were evaluated during
      <literal>EXECUTE</literal> to their values at prepare time, not to
@@ -258,26 +284,18 @@
     </para></listitem>
 
     <listitem><para>
-     Within a stored procedure, selecting from a table through a view
-     caused subsequent updates to the table to fail with a message that
-     the table was read-locked. (Bug #9597)
+     Within a stored procedure that selects from a table, invoking
+     another procedure that requires a write lock for the table caused
+     that procedure to fail with a message that the table was
+     read-locked. (Bug #9565)
     </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)
+     Within a stored procedure, selecting from a table through a view
+     caused subsequent updates to the table to fail with a message that
+     the table was read-locked. (Bug #9597)
     </para></listitem>
 
-   </itemizedlist>
-
-   <para>
-    Bugs fixed:
-   </para>
-
-   <itemizedlist>
-
     <listitem><para>
      For a stored procedure defined with <literal>SQL SECURITY
      DEFINER</literal> characteristic,
<literal>CURRENT_USER()</literal>
@@ -5035,6 +5053,17 @@
    <itemizedlist>
 
     <listitem><para>
+     <literal>SHOW BINARY LOGS</literal> displayed a file size of 0 for
+     all log files but the current one if the files were not located in
+     the data directory. (Bug #12004)
+    </para></listitem>
+
+    <listitem><para>
+     Server-side prepared statements failed for columns with a character
+     set of <literal>ucs2</literal>. (Bug #9442)
+    </para></listitem>
+
+    <listitem><para>
      References to system variables in an SQL statement prepared with
      <literal>PREPARE</literal> were evaluated during
      <literal>EXECUTE</literal> to their values at prepare time, not to
@@ -5189,6 +5218,18 @@
      describe the issue that was fixed. Use past tense. -->
 
    <itemizedlist>
+
+    <listitem><para>
+     The handling by the <literal>HEX()</literal> function of numbers
+     larger than 2<superscript>64</superscript> was improved. (Bug
+     #9854)
+    </para></listitem>
+
+    <listitem><para>
+     Added a missing mutex when rotating the relay logs. Also, the
+     server now logs an error message if the size of a relay log cannot
+     be read. (Bug #6987)
+    </para></listitem>
 
     <listitem><para>
      Added a missing mutex when rotating the relay logs. Also, the