bk commit - mysqldoc tree (marko:1.2854)

[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.2854 05/04/13 15:18:20 marko@stripped +1 -0
  manual.texi:
    News-4.1.12: Document fix of Bug #9802

  Docs/manual.texi
    1.2693 05/04/13 15:17:35 marko@stripped +7 -1
    News-4.1.12: Document fix of Bug #9802

# 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.2692/Docs/manual.texi	Wed Apr 13 13:01:32 2005
+++ 1.2693/Docs/manual.texi	Wed Apr 13 15:17:35 2005
@@ -68062,7 +68062,8 @@
 from MySQL 3.23.52 and 4.0.3.
 
 Setting @code{FOREIGN_KEY_CHECKS} to 0 can also be useful for ignoring
-foreign key constraints during @code{LOAD DATA} operations.
+foreign key constraints during @code{LOAD DATA} or @code{ALTER TABLE}
+operations.
 
 @code{InnoDB} does not allow you to drop a table that is
 referenced by a @code{FOREIGN KEY} constraint, unless
@@ -100595,6 +100596,11 @@
 Functionality added or changed:
 @itemize @bullet
 @item
+@code{InnoDB}: When @code{FOREIGN_KEY_CHECKS=0}, @code{ALTER TABLE} and
+@code{RENAME TABLE} will ignore any type incompatibilities between
+referencing and referenced columns.  Thus, it will be possible to convert
+the character sets of columns that participate in a foreign key.  Be sure
+to convert all tables before modifying any data!  (Bug #9802)
 
 @end itemize