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

[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.3446 05/08/31 15:10:50 paul@stripped +2 -0
  news-5.0.xml:
    Move note from features to bugs.
    Document bugfix. (Bug #10499)
    Document bugfix. (Bug #10056)
  news-4.1.xml:
    Document bugfix. (Bug #9645)
  news-5.0.xml, news-4.1.xml:
    Document bugfix. (Bug #4680)
  news-5.0.xml:
    Document bugfix. (Bug #12672)

  refman-common/news-5.0.xml
    1.108 05/08/31 15:09:57 paul@stripped +10 -10
    Move note from features to bugs.

  refman-common/news-5.0.xml
    1.107 05/08/31 15:01:28 paul@stripped +7 -0
    Document bugfix. (Bug #10499)

  refman-common/news-5.0.xml
    1.106 05/08/31 14:59:17 paul@stripped +8 -0
    Document bugfix. (Bug #10056)

  refman-common/news-4.1.xml
    1.61 05/08/31 14:55:20 paul@stripped +7 -0
    Document bugfix. (Bug #9645)

  refman-common/news-5.0.xml
    1.105 05/08/31 14:46:17 paul@stripped +12 -0
    Document bugfix. (Bug #4680)

  refman-common/news-4.1.xml
    1.60 05/08/31 14:46:17 paul@stripped +12 -0
    Document bugfix. (Bug #4680)

  refman-common/news-5.0.xml
    1.104 05/08/31 14:38:35 paul@stripped +7 -0
    Document bugfix. (Bug #12672)

# 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.59/refman-common/news-4.1.xml	2005-08-30 15:24:10 -05:00
+++ 1.61/refman-common/news-4.1.xml	2005-08-31 14:55:20 -05:00
@@ -180,6 +180,25 @@
 
       <listitem>
         <para>
+          Spatial index corruption could occur during updates. (Bug
+          #9645)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          If a <literal>DROP DATABASE</literal> fails on a master server
+          due to the presence of a non-database file in the database
+          directory, the master have have the database tables deleted,
+          but not the slaves. To deal with failed database drops, we now
+          write <literal>DROP TABLE</literal> statements to the binary
+          log for the tables so that they are dropped on slaves. (Bug
+          #4680)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <literal>DELETE</literal> or <literal>UPDATE</literal>
for an
           indexed <literal>MyISAM</literal> table could fail. This was
           due to a change in end-space comparison behavior from 4.0 to

--- 1.103/refman-common/news-5.0.xml	2005-08-31 12:21:39 -05:00
+++ 1.108/refman-common/news-5.0.xml	2005-08-31 15:09:57 -05:00
@@ -298,16 +298,6 @@
 
       <listitem>
         <para>
-          Natural joins and joins with <literal>USING</literal>,
-          including outer join variants, now are processed according to
-          the SQL:2003 standard. (Bug #4789, Bug #6136, Bug #6276, Bug
-          #6495, Bug #6558, Bug #9978, Bug #10646, Bug #10972, Bug
-          #11710)
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
           <literal>SHOW OPEN TABLES</literal> now supports
           <literal>FROM</literal> and <literal>LIKE</literal>
clauses.
           (Bug #12183)
@@ -376,6 +366,50 @@
     </para>
 
     <itemizedlist>
+
+      <listitem>
+        <para>
+          Natural joins and joins with <literal>USING</literal>,
+          including outer join variants, now are processed according to
+          the SQL:2003 standard. (Bug #4789, Bug #6136, Bug #6276, Bug
+          #6495, Bug #6558, Bug #9978, Bug #10646, Bug #10972, Bug
+          #11710)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          It was not possible to create a stored function with a spatial
+          return value data type. (Bug #10499)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          The only valid values for the <literal>PACK_KEYS</literal>
+          table option are 0 and 1, but other values were being
+          accepted. (Bug #10056)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          If a <literal>DROP DATABASE</literal> fails on a master server
+          due to the presence of a non-database file in the database
+          directory, the master have have the database tables deleted,
+          but not the slaves. To deal with failed database drops, we now
+          write <literal>DROP TABLE</literal> statements to the binary
+          log for the tables so that they are dropped on slaves. (Bug
+          #4680)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Improper use of loose index scan in <literal>InnoDB</literal>
+          sometimes caused incorrect query results. (Bug #12672)
+        </para>
+      </listitem>
 
       <listitem>
         <para>