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

[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.3403 05/08/26 14:06:54 paul@stripped +3 -0
  Revise change note.

  refman-common/news-5.0.xml
    1.82 05/08/26 14:06:52 paul@stripped +43 -39
    Revise change note.

  refman-common/news-4.1.xml
    1.54 05/08/26 14:06:52 paul@stripped +15 -11
    Revise change note.

  refman-common/news-4.0.xml
    1.25 05/08/26 14:06:52 paul@stripped +6 -2
    Revise change note.

# 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:	frost.snake.net
# Root:	/Volumes/frost2/MySQL/bk/mysqldoc

--- 1.24/refman-common/news-4.0.xml	2005-08-23 10:36:51 -05:00
+++ 1.25/refman-common/news-4.0.xml	2005-08-26 14:06:52 -05:00
@@ -847,8 +847,12 @@
 
       <listitem>
         <para>
-          Fixed a bug that caused the slave to stop on statements that
-          produced an error on the master. (Bug #8412)
+          Fixed a bug in replication that caused the master to stamp
+          generated statements (such as <literal>SET</literal> commands)
+          with an <literal>error_code</literal> intended only for
+          another statement. This could happen, for example, when a
+          statements generates a duplicate key error on the master but
+          must be replicated. (Bug #8412)
         </para>
       </listitem>
 

--- 1.53/refman-common/news-4.1.xml	2005-08-26 04:50:17 -05:00
+++ 1.54/refman-common/news-4.1.xml	2005-08-26 14:06:52 -05:00
@@ -177,27 +177,27 @@
     </remark>
 
     <itemizedlist>
-      
+
       <listitem>
         <para>
-          A <literal>SELECT DISTINCT</literal> query with a constant 
-          value for one of the columns would return only a single row.          
+          A <literal>SELECT DISTINCT</literal> query with a constant
+          value for one of the columns would return only a single row.
           (Bug #12625)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
-          Users created using an IP address or other alias rather than a 
-          hostname listed in <filename>/etc/hosts</filename> could not 
+          Users created using an IP address or other alias rather than a
+          hostname listed in <filename>/etc/hosts</filename> could not
           set their own passwords. (Bug #12302)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
-          <literal>NDB Cluster</literal>: An <literal>ALTER 
-          TABLE</literal> command caused loss of data stored prior to 
+          <literal>NDB Cluster</literal>: An <literal>ALTER
+          TABLE</literal> command caused loss of data stored prior to
           the issuing of the command. (Bug #12118)
         </para>
       </listitem>
@@ -3454,8 +3454,12 @@
 
       <listitem>
         <para>
-          Fixed a bug that caused the slave to stop on statements that
-          produced an error on the master. (Bug #8412)
+          Fixed a bug in replication that caused the master to stamp
+          generated statements (such as <literal>SET</literal> commands)
+          with an <literal>error_code</literal> intended only for
+          another statement. This could happen, for example, when a
+          statements generates a duplicate key error on the master but
+          must be replicated. (Bug #8412)
         </para>
       </listitem>
 

--- 1.81/refman-common/news-5.0.xml	2005-08-25 06:19:50 -05:00
+++ 1.82/refman-common/news-5.0.xml	2005-08-26 14:06:52 -05:00
@@ -162,50 +162,50 @@
     For a full list of changes, please refer to the changelog sections
     for each individual 5.0.x release.
   </para>
-  
+
   <section id="news-5-0-13">
-    
+
     <title id="title-news-5-0-13">&title-news-5-0-13;</title>
-    
+
     <para>
       Functionality added or changed:
     </para>
-    
+
 <!-- REPLACE WITH <itemizedlist> WHEN THERE ARE ITEMS FOR THIS LIST -->
-    
+
     <para>
       Bugs fixed:
     </para>
-    
+
     <itemizedlist>
-      
+
       <listitem>
         <para>
-          A query of the form <literal>SHOW TABLE STATUS FROM 
-          <replaceable>db_name</replaceable> WHERE name IN 
-          (<replaceable>select_query</replaceable>)</literal> would 
+          A query of the form <literal>SHOW TABLE STATUS FROM
+          <replaceable>db_name</replaceable> WHERE name IN
+          (<replaceable>select_query</replaceable>)</literal> would
           crash the server. (Bug #12636)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
-          Users created using an IP address or other alias rather than a 
-          hostname listed in <filename>/etc/hosts</filename> could not 
+          Users created using an IP address or other alias rather than a
+          hostname listed in <filename>/etc/hosts</filename> could not
           set their own passwords. (Bug #12302)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
-          Using <literal>DESCRIBE</literal> on a view after renaming a 
-          column in one of the view's base tables caused the server to 
+          Using <literal>DESCRIBE</literal> on a view after renaming a
+          column in one of the view's base tables caused the server to
           crash. (Bug #12533)
         </para>
       </listitem>
-    
+
     </itemizedlist>
-    
+
   </section>
 
   <section id="news-5-0-12">
@@ -217,18 +217,18 @@
     </para>
 
     <itemizedlist>
-      
+
       <listitem>
         <para>
-          <literal>NDB Cluster</literal>: An <literal>ALTER 
-          TABLE</literal> command caused loss of data stored prior to 
+          <literal>NDB Cluster</literal>: An <literal>ALTER
+          TABLE</literal> command caused loss of data stored prior to
           the issuing of the command. (Bug #12118)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
-          Natural outer joins are now processed according to the 
+          Natural outer joins are now processed according to the
           SQL:2003 standard. (Bug #6276, Bug #9978, Bug #10972)
         </para>
       </listitem>
@@ -315,29 +315,29 @@
     </para>
 
     <itemizedlist>
-      
+
       <listitem>
         <para>
-          A <literal>SELECT DISTINCT</literal> query with a constant 
-          value for one of the columns would return only a single row.          
+          A <literal>SELECT DISTINCT</literal> query with a constant
+          value for one of the columns would return only a single row.
           (Bug #12625)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
-          <literal>NDB Cluster</literal>: Cluster failed to take 
-          character set data into account when recomputing hashes (and 
-          thus could not locate records for updating or deletion) 
-          following a configuration change and node restart. (Bug 
+          <literal>NDB Cluster</literal>: Cluster failed to take
+          character set data into account when recomputing hashes (and
+          thus could not locate records for updating or deletion)
+          following a configuration change and node restart. (Bug
           #12220)
         </para>
       </listitem>
 
       <listitem>
         <para>
-          <literal>NDB Cluster</literal>: Wrong error message displayed 
-          when cluster management server closed port while 
+          <literal>NDB Cluster</literal>: Wrong error message displayed
+          when cluster management server closed port while
           <command>mysqld</command> was connecting. (Bug #10950)
         </para>
       </listitem>
@@ -4660,8 +4660,8 @@
           InnoDB: True <literal>VARCHAR</literal>: InnoDB stored the
           'position' of a row wrong in a column prefix primary key
           index; this could cause MySQL to complain <literal>ERROR 1032:
-          Can't find record …</literal> in an update of the primary key,
-          and also some <literal>ORDER BY</literal> or
+          Can't find record …</literal> in an update of the primary
+          key, and also some <literal>ORDER BY</literal> or
           <literal>DISTINCT</literal> queries. (Bug #9314)
         </para>
       </listitem>
@@ -5547,8 +5547,8 @@
       <listitem>
         <para>
           InnoDB: Relaxed locking in <literal>INSERT…SELECT</literal>,
-          single table <literal>UPDATE…SELECT</literal> and single
table
-          <literal>DELETE…SELECT</literal> clauses when
+          single table <literal>UPDATE…SELECT</literal> and single
+          table <literal>DELETE…SELECT</literal> clauses when
           <literal>innodb_locks_unsafe_for_binlog</literal> is used and
           isolation level of the transaction is not serializable.
           <literal>InnoDB</literal> uses consistent read in these cases
@@ -6518,8 +6518,12 @@
 
       <listitem>
         <para>
-          Fixed a bug that caused the slave to stop on statements that
-          produced an error on the master. (Bug #8412)
+          Fixed a bug in replication that caused the master to stamp
+          generated statements (such as <literal>SET</literal> commands)
+          with an <literal>error_code</literal> intended only for
+          another statement. This could happen, for example, when a
+          statements generates a duplicate key error on the master but
+          must be replicated. (Bug #8412)
         </para>
       </listitem>