bk commit - mysqldoc tree (marko:1.2760)

[Marko Mäkelä]

Below is the list of changes that have just been committed into a local
mysqldoc repository of marko. When marko 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.2760 05/03/22 15:44:55 marko@stripped +1 -0
  manual.texi:
    InnoDB restrictions: Note that InnoDB supports prefix indexes since 4.0.14.

  Docs/manual.texi
    1.2594 05/03/22 15:44:18 marko@stripped +5 -4
    InnoDB restrictions: Note that InnoDB supports prefix indexes since 4.0.14.

# 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:	marko
# Host:	hundin.mysql.fi
# Root:	/home/marko/k/mysqldoc

--- 1.2593/Docs/manual.texi	Tue Mar 22 15:37:19 2005
+++ 1.2594/Docs/manual.texi	Tue Mar 22 15:44:18 2005
@@ -70707,15 +70707,16 @@
 The row count is only a rough estimate used in SQL optimization.
 
 @item
-If you try to create a unique index on a prefix of a column you get an
-error:
+Before MySQL 4.0.14 or 4.1.0, if you tried to create a unique index on a
+prefix of a column you got an error:
 
 @example
 CREATE TABLE T (A CHAR(20), B INT, UNIQUE (A(5))) TYPE = InnoDB;
 @end example
 
-If you create a non-unique index on a prefix of a column, @code{InnoDB}
-creates an index over the whole column.
+If you created a non-unique index on a prefix of a column, @code{InnoDB}
+created an index over the whole column.  These restrictions were removed
+in MySQL 4.0.14.
 
 @item
 Before MySQL 4.0.20 or 4.1.2, the MySQL @code{LOCK TABLES} operation