bk commit - mysqldoc@docsrva tree (heikki:1.2804)

[Heikki Tuuri]

Below is the list of changes that have just been committed into a local
mysqldoc repository of heikki. When heikki 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.2804 05/06/16 19:18:41 heikki@stripped +2 -0
  news.xml, innodb.xml:
    Document better InnoDB FOREIGN KEY handling, and document some bug fixes in 5.0.7

  refman/news.xml
    1.2 05/06/16 19:18:35 heikki@stripped +13 -0
    Document better InnoDB FOREIGN KEY handling, and document some bug fixes in 5.0.7

  refman/innodb.xml
    1.3 05/06/16 19:18:34 heikki@stripped +20 -7
    Document better InnoDB FOREIGN KEY handling, and document some bug fixes in 5.0.7

# 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:	heikki
# Host:	hundin.mysql.fi
# Root:	/home/heikki/bk

--- 1.2/refman/innodb.xml	Thu Jun 16 14:19:23 2005
+++ 1.3/refman/innodb.xml	Thu Jun 16 19:18:34 2005
@@ -1826,7 +1826,8 @@
    <itemizedlist>
 
     <listitem><para>
-     Both tables must be <literal>InnoDB</literal> type.
+     Both tables must be <literal>InnoDB</literal> type and they must
+     not be temporary tables.
     </para></listitem>
 
     <listitem><para>
@@ -1851,6 +1852,12 @@
      length.
     </para></listitem>
 
+    <listitem><para>
+     If the <literal>CONSTRAINT<replaceable>symbol</replaceable></literal>
+     is given, it must be unique in the database. If it is not given,
+     <literal>InnoDB</literal> creates the name automatically. 
+    </para></listitem>
+
    </itemizedlist>
 
    <para>
@@ -1878,6 +1885,9 @@
      in the child table. <literal>ON DELETE CASCADE</literal> is
      available starting from MySQL 3.23.50 and <literal>ON UPDATE
      CASCADE</literal> is available starting from 4.0.8.
+     You should not define several <literal>ON UPDATE CASCADE</literal>
+     clauses that act on the same column in the parent table or in the
+     child table.
     </para></listitem>
 
     <listitem><para>
@@ -1939,9 +1949,10 @@
    <para>
     <literal>InnoDB</literal> needs indexes on foreign keys and
     referenced keys so that foreign key checks can be fast and not
-    require a table scan. Starting with MySQL 4.1.2, these indexes are
-    created automatically. In older versions, the indexes must be
-    created explicitly or the creation of foreign key constraints fails.
+    require a table scan. Starting with MySQL 4.1.2, the index on
+    the foreign key is created automatically. In older versions, the
+    indexes must be created explicitly or the creation of foreign key
+    constraints fails.
    </para>
 
    <para>
@@ -6104,14 +6115,16 @@
    </para></listitem>
 
    <listitem><para>
-    The maximum row length, except for <literal>BLOB</literal> and
+    The maximum row length, except for <literal>VARCHAR</literal>,
+    <literal>BLOB</literal> and
     <literal>TEXT</literal> columns, is slightly less than half of a
     database page. That is, the maximum row length is about 8000 bytes.
     <literal>LONGBLOB</literal> and <literal>LONGTEXT</literal> columns
     must be less than 4GB, and the total row length, including also
     <literal>BLOB</literal> and <literal>TEXT</literal> columns, must be
-    less than 4GB. <literal>InnoDB</literal> stores the first 512 bytes
-    of a <literal>BLOB</literal> or <literal>TEXT</literal> column in
+    less than 4GB. <literal>InnoDB</literal> stores the first 768 bytes
+    of a <literal>VARCHAR</literal>,
+    <literal>BLOB</literal>, or <literal>TEXT</literal> column in
     the row, and the rest into separate pages.
    </para></listitem>
 

--- 1.1/refman/news.xml	Thu Jun 16 02:46:58 2005
+++ 1.2/refman/news.xml	Thu Jun 16 19:18:35 2005
@@ -595,6 +595,19 @@
     </para></listitem>
 
     <listitem><para>
+     <literal>InnoDB</literal>: Fixed a duplicate key error that occurred
+     with <literal>REPLACE</literal> in a table with an
+     <literal>AUTO-INC</literal> column. (Bug #11005)
+    </para></listitem>
+
+    <listitem><para>
+     Fixed that MySQL would pass a wrong key length to storage engines
+     in <literal>MIN()</literal>. This could cause warnings
+     <literal>InnoDB: Warning: using a partial-field key prefix in
+     search.</literal> in the <filename>.err</filename> log. (Bug #11039)
+    </para></listitem>
+
+    <listitem><para>
      Fixed a server crash for <literal>INSERT</literal> or
      <literal>UPDATE</literal> when the <literal>WHERE</literal> clause
      contained a correlated subquery that referred to a column of the