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

[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.3584 05/09/16 21:34:43 paul@stripped +1 -0
  news-5.0.xml:
    Document bugfix. (Bug #12291)

  refman-common/news-5.0.xml
    1.205 05/09/16 21:29:27 paul@stripped +18 -9
    Document bugfix. (Bug #12291)

# 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:	/Users/paul/bk/mysqldoc

--- 1.204/refman-common/news-5.0.xml	2005-09-16 09:14:37 -05:00
+++ 1.205/refman-common/news-5.0.xml	2005-09-16 21:29:27 -05:00
@@ -189,6 +189,15 @@
 
       <listitem>
         <para>
+          If, while processing a join, the server switched from
+          sequentially scanning a table for early passes to using an
+          index for a later pass, incorrect scan initialization could
+          result in an error or server crash. (Bug #12291)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           For queries with <literal>DISTINCT</literal> and <literal>WITH
           ROLLUP</literal>, the <literal>DISTINCT</literal> should be
           applied after the rollup operation, but was not always. (Bug
@@ -323,14 +332,14 @@
     </para>
 
     <itemizedlist>
-      
+
       <listitem>
         <para>
-          <literal>NDB</literal>: A cluster shutdown following the 
-          crash of a data node would fail to terminate the remaining 
-          node processes, even though <command>ndb_mgm</command> showed
-          the shutdown request as having been completed. (Bug #10938, 
-          Bug #9996, Bug #11623)
+          <literal>NDB</literal>: A cluster shutdown following the crash
+          of a data node would fail to terminate the remaining node
+          processes, even though <command>ndb_mgm</command> showed the
+          shutdown request as having been completed. (Bug #10938, Bug
+          #9996, Bug #11623)
         </para>
       </listitem>
 
@@ -2299,11 +2308,11 @@
     </para>
 
     <itemizedlist>
-      
+
       <listitem>
         <para>
-          <literal>NDB</literal>: Trying to use a greater number of 
-          tables then specified by the value of 
+          <literal>NDB</literal>: Trying to use a greater number of
+          tables then specified by the value of
           <literal>MaxNoOfTables</literal> caused table corruption such
           that data nodes could not be restarted. (Bug #9994)
         </para>