bk commit - mysqldoc tree (1.350)

Below is the list of changes that have just been committed into a local
mysqldoc repository of arjen. When arjen 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.350 03/03/25 06:55:47 arjen@xxxxxxxxxxxxxxxxxx +1 -0
  Fixups of Monty-commit 1.322

  Docs/manual.texi
    1.327 03/03/25 06:55:45 arjen@xxxxxxxxxxxxxxxxxx +12 -14
    Fixups of Monty-commit 1.322

# 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: arjen
# Host: george.bitbike.com
# Root: /home/arjen/mysqldoc

--- 1.326/Docs/manual.texi      Tue Mar 25 07:15:32 2003
+++ 1.327/Docs/manual.texi      Tue Mar 25 06:55:45 2003
@@ -3572,13 +3572,13 @@
 The reason for this is due to the fact that HEAP tables, which are used
 first for temporary tables, are not capable of handling VARCHAR columns.
 
-This behaviour will be fixed in one of 4.1 releases.
+This behaviour will be fixed in one of the 4.1 series releases.
 
 @item
-Because of how table definitions files are stored one can't have use
-character 255 CHAR(255) in table names, column names or enums. This is
-sheduled to be fixed in 5.1 when we have a new table definition format
-files.
+Because of how table definitions files are stored one can't use
+character 255 (@code{CHAR(255)}) in table names, column names or enums.
+This is sheduled to be fixed in version 5.1 when we have new table
+definition format files.
 
 @item
 When using @code{SET CHARACTER SET}, one can't use translated
@@ -33571,7 +33571,8 @@
 Note that the return value is converted to a @code{BIGINT}!
 
 @findex ROUND()
-@item ROUND(X[,D])
+@item ROUND(X)
+@itemx ROUND(X,D)
 Returns the argument @code{X}, rounded to the nearest integer.
 With two arguments rounded to a number to @code{D} decimals.
 @example
@@ -33595,15 +33596,15 @@
 like @code{TRUNCATE()} or @code{FLOOR()} instead.
 
 @findex DIV
-@itemx DIV
 @item DIV
-Integer division. Ssimilar to @code{FLOOR()} but is safe with bigint values.
+Integer division.
+Similar to @code{FLOOR()} but safe with @code{BIGINT} values.
 @example
 mysql> SELECT 5 DIV 2
        -> 2
 @end example
 
-This is new in MySQL 4.1.0.
+@code{DIV} is new in MySQL 4.1.0.
 
 @findex EXP()
 @item EXP(X)
@@ -34195,9 +34196,6 @@
 with a @samp{-} for negative intervals.  @code{type} is a keyword indicating
 how the expression should be interpreted.
 
-The related function @code{EXTRACT(type FROM date)} returns the 'type'
-interval from the date.
-
 The following table shows how the @code{type} and @code{expr} arguments
 are related:
 
@@ -52900,8 +52898,8 @@
 Functionality added or changed:
 @itemize
 @item
-When using a not existing table type with @code{CREATE TABLE}, first
-try if the default table type exists before falling back to MyISAM.
+When using a non-existing table type with @code{CREATE TABLE}, first
+try if the default table type exists before falling back to @code{MyISAM}.
 @item
 Fixed wrong hostname for TCP/IP connections displayed in
 @code{SHOW PROCESSLIST}.

-- 
MySQL Internals Mailing List
For list archives: http://lists.mysql.com/internals
To unsubscribe:    
http://lists.mysql.com/internals?unsub=gcdmd-internals@xxxxxxxxxxx