bk commit - mysqldoc tree (monty:1.2665)

[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.2665 05/05/13 23:01:44 monty@stripped +1 -0
  merge

  Docs/manual.texi
    1.2856 05/05/13 23:01:39 monty@stripped +3 -3
    merge

# 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-old/RESYNC

--- 1.2855/Docs/manual.texi	2005-05-13 19:40:11 +03:00
+++ 1.2856/Docs/manual.texi	2005-05-13 23:01:39 +03:00
@@ -51637,6 +51637,17 @@
 mysql> SELECT SUBDATE('1998-01-02 12:00:00', 31);
         -> '1997-12-02 12:00:00'
 @end example
+
+@strong{Note} that you can't use format @code{"%X%V"} to convert a year-week
+string to date as a year-week doesn't uniquely identify a year-month if the
+week crosses a month boundary.  If you want to convert a year-week to a date
+you can do it by also specifying the week day:
+
+@example
+mysql> select str_to_date('200442 Monday', '%X%V %W');
+-> 2004-10-18
+@end example
+
 @c end_description_for_help_topic
 
 @c description_for_help_topic SUBTIME
@@ -55140,6 +55151,10 @@
 mysql> INSERT INTO @var{tbl_name} () VALUES();
 @end example
 
+In @code{STRICT} mode you will get an error if a column doesn't have a
+default value. In not @code{strict} mode, MySQL will use the implicit
+default value for any column with a not defined default value.
+
 @item
 You can specify an expression @var{expr} to provide a column value.
 This might involve type conversion if the type of the expression does not
@@ -59156,22 +59171,21 @@
 
 @end itemize
 
-@c TODO: uncomment the following stuff when Bug #5986 gets fixed
+Suppose a table @code{t} is defined as follows:
 
-@c Suppose a table @code{t} is defined as follows:
-@c
-@c @example
-@c CREATE TABLE t (i INT NOT NULL);
-@c @end example
-@c
-@c In this case, @code{i} has no explicit default, so all of the following
-@c statements produce an error in strict mode and no row is inserted:
-@c
-@c @example
-@c INSERT INTO t VALUES();
-@c INSERT INTO t VALUES(DEFAULT);
-@c INSERT INTO t VALUES(DEFAULT(i));
-@c @end example
+@example
+CREATE TABLE t (i INT NOT NULL);
+@end example
+
+In this case, @code{i} has no explicit default, so all of the following
+statements produce an error in strict mode and no row is inserted:
+For non strict mode, only the last statement produces an error.
+
+@example
+INSERT INTO t VALUES();
+INSERT INTO t VALUES(DEFAULT);
+INSERT INTO t VALUES(DEFAULT(i));
+@end example
 
 @xref{Server SQL mode}.
 
@@ -62160,7 +62174,7 @@
 SHOW [BDB] LOGS
 SHOW PRIVILEGES
 SHOW [FULL] PROCESSLIST
-SHOW STATUS [LIKE '@var{pattern}']
+SHOW [GLOBAL | SESSION] STATUS [LIKE '@var{pattern}']
 SHOW TABLE STATUS [FROM @var{db_name}] [LIKE '@var{pattern}']
 SHOW [OPEN] TABLES [FROM @var{db_name}] [LIKE '@var{pattern}']
 SHOW [GLOBAL | SESSION] VARIABLES [LIKE '@var{pattern}']
@@ -62986,7 +63000,7 @@
 @cindex variables, status
 
 @example
-SHOW STATUS [LIKE '@var{pattern}']
+SHOW [GLOBAL | SESSION] STATUS [LIKE '@var{pattern}']
 @end example
 
 @cindex @command{mysqladmin}
@@ -63043,6 +63057,14 @@
 +--------------------+----------+
 @end example
 
+The @code{GLOBAL} and @code{SESSION} options are new in MySQL 5.0.2 With
+@code{GLOBAL}, you get the status values for all connections to
+MySQL. With @code{SESSION}, you get the status values for
+the current connection. If you use neither option, the default is
+@code{SESSION}. @code{LOCAL} is a synonym for @code{SESSION}.
+
+Note that some status variables only have a global value. For these you get
+the same value for both @code{GLOBAL} and @code{SESSION}.
 
 @node SHOW TABLE STATUS, SHOW TABLES, SHOW STATUS, SHOW
 @subsubsection @code{SHOW TABLE STATUS} Syntax
@@ -100147,6 +100169,9 @@
 last table checked in @code{--auto-repair} mode returned an error (such
 as the table being a @code{MERGE} table).  (Bug #9492)
 @item
+@code{SET @@var= CAST(NULL AS [INTEGER|CHAR])} now sets the result type of
+the variable to @code{INTEGER}/@code{CHAR}. (Bug #6598)
+@item
 Incorrect results were returned for queries of the form @code{SELECT ... LEFT
 JOIN ... WHERE EXISTS (@var{subquery})}, where the subquery selected rows
 based on an @code{IS NULL} condition.  (Bug #9516)
@@ -101130,6 +101155,9 @@
 Functionality added or changed:
 @itemize @bullet
 @item
+@code{SHOW STATUS} now shows the thread specific status variables and
+@code{SHOW GLOBAL STATUS} shows the status variables for the whole server.
+@item
 Added support for the @code{INFORMATION_SCHEMA} ``information database'' that
 provides database metadata.
 @xref{INFORMATION_SCHEMA,  , @code{INFORMATION_SCHEMA}}.
@@ -101827,6 +101855,19 @@
 @item
 Fixed a portability problem in compiling @file{mysql.cc} with @command{VC++}
 on Windows.  (Bug #10245)
+@item
+@code{CAST(string_argument AS UNSIGNED)} didn't work for big integers above the
+signed range.  Now this function and @code{CAST(string_argument AS SIGNED)}
+also produces warnings for wrong string arguments. (Bug #7036) 
+@item
+Fixed compile problem with MinGW. Thanks to Nils Durner for patch!
+(Bug #8872) 
+@item
+MySQL doesn't anymore automaticly block IP's for which
+@code{gethostbyname_r()} fails when the reason is that the DNS server is down.
+Thanks to Jeremy Cole for patch. (Bug #8467)
+@item
+Fixed bug in keycache that caused core dump. (Bug #10167)
 @item
 The @code{--delimiter} option for the @command{nds_select} program was
 non-functional.  (Bug #10287)