bk commit into mysqldoc tree (1.249)

Below is the list of changes that have just been committed into a local
mysqldoc repository of monty. When monty 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.249 03/02/27 11:22:21 monty@xxxxxxxxxxxxxxx +1 -0
  4.0 changelog

  Docs/manual.texi
    1.230 03/02/27 11:22:21 monty@xxxxxxxxxxxxxxx +10 -0
    4.0 changelog

# 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: monty
# Host: narttu.mysql.fi
# Root: /my/mysqldoc

--- 1.229/Docs/manual.texi      Tue Feb 25 14:20:07 2003
+++ 1.230/Docs/manual.texi      Thu Feb 27 11:22:21 2003
@@ -52422,6 +52422,13 @@
 
 Bugs fixed:
 @itemize
+@item
+On windows, @code{STOP SLAVE} didn't stop the slave until the slave
+got one new command from the master.
+@item
+Integer values between 9223372036854775807 and 9999999999999999999 are now
+regarded as unsigned longlongss, not as floats. This make these values work
+similar to values between 10000000000000000000 and 18446744073709551615.
 @end itemize
 
 @node News-4.0.11, News-4.0.10, News-4.0.12, News-4.0.x
@@ -53782,6 +53789,9 @@
 @node News-3.23.56, News-3.23.55, News-3.23.x, News-3.23.x
 @appendixsubsec Changes in release 3.23.56 (not released yet)
 @itemize
+@item
+@code{Comment} column in @code{SHOW TABLE STATUS} now reports that it can
+contain NULL values (which is the case for a crashed .frm file).
 @item
 Fixed a problem with @code{BLOB NOT NULL} columns used with @code{IS NULL}.
 @item

---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail internals-thread7209@xxxxxxxxxxxxxxx
To unsubscribe, e-mail <internals-unsubscribe@xxxxxxxxxxxxxxx>