bk commit - mysqldoc tree (monty:1.2788)

[monty]

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.2788 05/04/04 15:12:31 monty@stripped +1 -0
  More DECIMAL information
  Changelog for 5.0.4

  Docs/manual.texi
    1.2617 05/04/04 15:12:26 monty@stripped +44 -9
    More DECIMAL information
    Changelog for 5.0.4

# 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.com
# Root:	/home/my/mysqldoc

--- 1.2616/Docs/manual.texi	2005-03-31 01:42:42 +03:00
+++ 1.2617/Docs/manual.texi	2005-04-04 15:12:26 +03:00
@@ -196,6 +196,10 @@
 or operating systems, see @ref{Porting}.
 
 @item
+For information about upgrading from a Version 4.1 release, see
+@ref{Upgrading-from-4.1}.
+
+@item
 For information about upgrading from a Version 4.0 release, see
 @ref{Upgrading-from-4.0}.
 
@@ -204,10 +208,6 @@
 @ref{Upgrading-from-3.23}.
 
 @item
-For information about upgrading from a Version 3.22 release, see
-@ref{Upgrading-from-3.22}.
-
-@item
 For a tutorial introduction to the MySQL Database Server,
 see @ref{Tutorial}.
 
@@ -10644,6 +10644,16 @@
 @itemize @bullet
 
 @item
+@code{DECIMAL} columns are now stored in a more efficient format.
+To convert a table to use the new @code{DECIMAL} type, you should do an
+@code{ALTER TABLE} on it. The @code{ALTER TABLE} will also change all your
+@code{VARCHAR} columns to use the new @code{VARCHAR} column type.
+
+@item
+MySQL 5.0.3 now uses precision math when calculating with @code{DECIMAL}
+values (64 decimal digits).
+
+@item
 As of MySQL 5.0.3, trailing spaces no longer are removed from values stored
 in @code{VARCHAR} and @code{VARBINARY} columns.  The maximum length for
 @code{VARCHAR} or @code{VARBINARY} now is 65,535 characters or bytes,
@@ -43881,6 +43891,10 @@
 @code{CONVERT(... USING ...)} is implemented according to the standard SQL
 specification.
 
+If you in @code{traditional} mode convert a zero date string to a date
+@code{CONVERT()} will return NULL. MySQL 5.0.4 and above will also produce
+a warning.
+
 @node Charset-CAST, Charset-SHOW, Charset-CONVERT, Charset-operations
 @subsection @code{CAST()}
 
@@ -43914,6 +43928,9 @@
 SELECT CAST(_latin1'test' AS CHAR CHARACTER SET utf8) COLLATE utf8_bin;
 @end example
 
+If you in @code{traditional} mode cast a zero date string to a date
+@code{CAST()} will return NULL. MySQL 5.0.4 and above will also produce
+a warning.
 
 @node Charset-SHOW,  , Charset-CAST, Charset-operations
 @subsection @code{SHOW} Statements
@@ -48523,6 +48540,11 @@
 Returns the index of @var{str} in the @var{str1}, @var{str2},
 @var{str3}, @code{...} list.
 Returns @code{0} if @var{str} is not found.
+
+If all arguments to FIELD() are strings, then all arguments are compared
+as strings. If all arguments are numbers then they are compared as
+numbers.  Otherwise the arguments are compared as double.
+
 If @var{str} is @code{NULL}, the return value is @code{0} because
 @code{NULL} fails equality comparison with any value.
 @code{FIELD()} is the complement of @code{ELT()}.
@@ -57643,11 +57665,12 @@
 @item
 @code{IGNORE} is a MySQL extension to standard SQL.
 It controls how @code{ALTER TABLE} works if there are duplicates on
-unique keys in the new table.
+unique keys in the new table or if one got warnings during @code{STRICT} mode.
 If @code{IGNORE} isn't specified, the copy is aborted and rolled back if
 duplicate-key errors occur.
 If @code{IGNORE} is specified, then for rows with duplicates on a unique
-key, only the first row is used. The others are deleted.
+key, only the first row is used. The others conflicting rows are deleted.
+Wrong values are truncated to the closest matching acceptable value.
 
 @item
 You can issue multiple @code{ADD}, @code{ALTER}, @code{DROP}, and
@@ -97920,6 +97943,9 @@
 Functionality added or changed:
 @itemize @bullet
 @item
+Invalid @code{DEFAULT} values for @code{CREATE TABLE} now generates errors.
+(Bug #5902)
+@item
 Added @code{--show-table-type} option to @command{mysqlshow}, to display a
 column indicating the table type, as in @code{SHOW FULL TABLES}.  (Bug #5036)
 @item
@@ -97932,11 +97958,20 @@
 Bugs fixed:
 @itemize @bullet
 @item
-Inserting a zero date in a @code{DATETIME} field during @code{traditional} mode
-now produces an error.
+@code{CAST()} now produces warnings when casting a wrong @code{INTEGER}
+and @code{CHAR} values. This also applies to implicite @code{string} to
+@code{number} casts. (Bug #5912)
+@item
+@code{ALTER TABLE} now fails in @code{STRICT} mode if generates warnings.
+@item
+Using @code{CONVERT('0000-00-00',date)} or @code{CAST('0000-00-00' as date)}
+in @code{traditional} mode now produces a warning. (Bug #6145)
+@item
+Inserting a zero date in a @code{DATE}, @code{DATETIME} or @code{TIMESTAMP}
+column during @code{TRADITIONAL} mode now produces an error. (Bug #5933)
 @item
 @code{STR_TO_DATE()} now produces warnings in normal mode and errors in
-@code{strict mode}.
+@code{strict mode}. (Bug #5902)
 @item
 Fixed a problem with @code{ORDER BY} that sometimes caused incorrect sorting
 of @code{utf8} data.  (Bug #9309)