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

[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.3054 05/07/18 14:35:16 paul@stripped +3 -0
  Document bugfix. (Bug #7403)
  Document bugfix. (Bug #9359)
  Document bugfix. (Bug #9597)
  Document bugfix. (Bug #11853)
  Document bugfix. (Bug #11893)

  refman/news.xml
    1.78 05/07/18 14:35:15 paul@stripped +50 -0
    Document bugfix. (Bug #7403)
    Document bugfix. (Bug #9359)
    Document bugfix. (Bug #9597)
    Document bugfix. (Bug #11853)
    Document bugfix. (Bug #11893)

  refman-5.0/news.xml
    1.64 05/07/18 14:35:15 paul@stripped +35 -0
    Sync.

  refman-4.1/news.xml
    1.55 05/07/18 14:35:15 paul@stripped +15 -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.54/refman-4.1/news.xml	2005-07-16 20:16:42 -05:00
+++ 1.55/refman-4.1/news.xml	2005-07-18 14:35:15 -05:00
@@ -195,6 +195,21 @@
    <itemizedlist>
 
     <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
+     their values at execution time. (Bug #9359)
+    </para></listitem>
+
+    <listitem><para>
+     For server shutdown on Windows, error messages of the form
+     <literal>Forcing close of thread <replaceable>n</replaceable>
user:
+     '<replaceable>name</replaceable>'</literal> were being written to
+     the error log. Now connections are closed more gracefully without
+     generating error messages. (Bug #7403)
+    </para></listitem>
+
+    <listitem><para>
      Corrected a problem with the optimizer incorrectly adding
      <literal>NOT NULL</literal> constraints, producing in incorrect
      results for complex queries. (Bug #11482)

--- 1.63/refman-5.0/news.xml	2005-07-17 21:02:23 -05:00
+++ 1.64/refman-5.0/news.xml	2005-07-18 14:35:15 -05:00
@@ -237,6 +237,41 @@
     </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
+     their values at execution time. (Bug #9359)
+    </para></listitem>
+
+    <listitem><para>
+     For server shutdown on Windows, error messages of the form
+     <literal>Forcing close of thread <replaceable>n</replaceable>
user:
+     '<replaceable>name</replaceable>'</literal> were being written to
+     the error log. Now connections are closed more gracefully without
+     generating error messages. (Bug #7403)
+    </para></listitem>
+
+    <listitem><para>
+     Increased the version number of the
+     <literal>libmysqlclient</literal> shared library from 14 to 15
+     because it is binary incompatible with the MySQL 4.1 client
+     library. (Bug #11893)
+    </para></listitem>
+
+    <listitem><para>
+     A recent optimizer change caused <literal>DELETE &hellip; WHERE
+     &hellip; NOT LIKE</literal> and <literal>DELETE &hellip; WHERE
+     &hellip; NOT BETWEEN</literal> to not properly identify the rows to
+     be deleted. (Bug #11853)
+    </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)
+    </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,

--- 1.77/refman/news.xml	2005-07-17 21:02:22 -05:00
+++ 1.78/refman/news.xml	2005-07-18 14:35:15 -05:00
@@ -229,6 +229,41 @@
     </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
+     their values at execution time. (Bug #9359)
+    </para></listitem>
+
+    <listitem><para>
+     For server shutdown on Windows, error messages of the form
+     <literal>Forcing close of thread <replaceable>n</replaceable>
user:
+     '<replaceable>name</replaceable>'</literal> were being written to
+     the error log. Now connections are closed more gracefully without
+     generating error messages. (Bug #7403)
+    </para></listitem>
+
+    <listitem><para>
+     Increased the version number of the
+     <literal>libmysqlclient</literal> shared library from 14 to 15
+     because it is binary incompatible with the MySQL 4.1 client
+     library. (Bug #11893)
+    </para></listitem>
+
+    <listitem><para>
+     A recent optimizer change caused <literal>DELETE &hellip; WHERE
+     &hellip; NOT LIKE</literal> and <literal>DELETE &hellip; WHERE
+     &hellip; NOT BETWEEN</literal> to not properly identify the rows to
+     be deleted. (Bug #11853)
+    </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)
+    </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,
@@ -4998,6 +5033,21 @@
      describe the issue that was fixed. Use past tense. -->
 
    <itemizedlist>
+
+    <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
+     their values at execution time. (Bug #9359)
+    </para></listitem>
+
+    <listitem><para>
+     For server shutdown on Windows, error messages of the form
+     <literal>Forcing close of thread <replaceable>n</replaceable>
user:
+     '<replaceable>name</replaceable>'</literal> were being written to
+     the error log. Now connections are closed more gracefully without
+     generating error messages. (Bug #7403)
+    </para></listitem>
 
     <listitem><para>
      Corrected a problem with the optimizer incorrectly adding