[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mysql-internals
Subject:    bk commit - mysqldoc tree (paul:1.1200)
From:       paul () mysql ! com
Date:       2004-01-31 5:37:11
Message-ID: 20040131053711.59B8023A4E5 () ice ! snake ! net
[Download RAW message or body]

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.1200 04/01/30 23:37:06 paul@ice.snake.net +1 -0
  Document behavior of mysqldump for -inf/inf.

  Docs/manual.texi
    1.1106 04/01/30 23:37:03 paul@ice.snake.net +35 -3
    Document behavior of mysqldump for -inf/inf.

# 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:	ice.snake.net
# Root:	/Volumes/ice2/MySQL/bk/mysqldoc

--- 1.1105/Docs/manual.texi	Fri Jan 30 12:12:04 2004
+++ 1.1106/Docs/manual.texi	Fri Jan 30 23:37:03 2004
@@ -30893,7 +30893,8 @@
 @cindex backing up, databases
 
 @cindex @code{mysqldump}
-Utility to dump a database or a collection of database for backup or for
+The @code{mysqldump} client can be used
+to dump a database or a collection of database for backup or for
 transferring the data to another SQL server (not necessarily a MySQL
 server).  The dump will contain SQL statements to create the table
 and/or populate the table.
@@ -30913,14 +30914,45 @@
 You can get a list of the options your version of @code{mysqldump} supports
 by executing @code{mysqldump --help}.
 
-Note that if you run @code{mysqldump} without @code{--quick} or
+If you run @code{mysqldump} without @code{--quick} or
 @code{--opt}, @code{mysqldump} will load the whole result set into
 memory before dumping the result.  This will probably be a problem if
 you are dumping a big database.
 
-Note that if you are using a new copy of the @code{mysqldump} program
+If you are using a recent copy of the @code{mysqldump} program
 and you are going to do a dump that will be read into a very old MySQL
 server, you should not use the @code{--opt} or @code{-e} options.
+
+Out-of-range numeric values such as @code{-inf} and @code{inf}, as well
+as NaN (not-a-number) values are dumped by @code{mysqldump} as @code{NULL}.
+You can see this using the following example table:
+
+@example
+mysql> CREATE TABLE t (f DOUBLE);
+mysql> INSERT INTO t VALUES(1e+111111111111111111111);
+mysql> INSERT INTO t VALUES(-1e111111111111111111111);
+mysql> SELECT f FROM t;
++------+
+| f    |
++------+
+|  inf |
+| -inf |
++------+
+@end example
+
+For this table, @code{mysqldump} produces the following data output:
+
+@example
+--
+-- Dumping data for table `t`
+--
+
+INSERT INTO t VALUES (NULL);
+INSERT INTO t VALUES (NULL);
+@end example
+
+The significance of this behavior is that if you dump and restore the
+table, the new table has contents that differ from the original contents.
 
 @code{mysqldump} supports the following options:
 

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

[prev in list] [next in list] [prev in thread] [next in thread]