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

[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.2736 05/06/08 15:58:14 paul@stripped +1 -0
  manual.texi:
    Add note about convering CHAR/VARCHAR BINARY to
    BINARY/VARBINARY for 4.0 -> 4.1 upgrade.

  Docs/manual.texi
    1.2952 05/06/08 15:57:41 paul@stripped +16 -7
    Add note about convering CHAR/VARCHAR BINARY to
    BINARY/VARBINARY for 4.0 -> 4.1 upgrade.

# 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:	/Volumes/frost2/MySQL/bk/mysqldoc

--- 1.2951/Docs/manual.texi	2005-06-08 15:44:13 -05:00
+++ 1.2952/Docs/manual.texi	2005-06-08 15:57:41 -05:00
@@ -10559,6 +10559,7 @@
 @code{MyISAM} tables with live checksum enabled (you used @code{CHECKSUM=1} in
 @code{CREATE TABLE} or @code{ALTER TABLE}), these tables will appear corrupted.
 Use @code{REPAIR TABLE} to recalculate the checksum.
+
 @end itemize
 
 @item
@@ -10608,13 +10609,21 @@
 the @code{timezone} system variable was renamed to @code{system_time_zone}.
 
 @item
-All tables and string columns have a character set.
-@xref{Charset}.
-Character set information is displayed by
-@code{SHOW CREATE TABLE} and @command{mysqldump}.
-(MySQL versions 4.0.6 and above can read the new dump files; older
-versions cannot.)
-This change should not affect applications that use only one character set.
+All tables and non-binary string columns (@code{CHAR}, @code{VARCHAR}, and
+@code{TEXT}) have a character set.  @xref{Charset}.  Binary string columns
+(@code{BINARY}, @code{VARBINARY}, and @code{BLOB}) contain strings of bytes
+and do not have a character set.
+
+Character set information is displayed by @code{SHOW CREATE TABLE} and
+@command{mysqldump}.  (MySQL versions 4.0.6 and above can read the new dump
+files; older versions cannot.) This change should not affect applications
+that use only one character set.
+
+@item
+If you were using columns with the @code{CHAR BINARY} or @code{VARCHAR
+BINARY} data types in MySQL 4.0, these were treated as binary strings.  To
+have them treated as binary strings in MySQL 4.1, you should convert them to
+use the @code{BINARY} and @code{VARBINARY} data types, respectively.
 
 @item
 If you have table columns that