bk commit - mysqldoc@docsrva tree (paul:1.3211)

[paul]

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.3211 05/08/08 16:39:30 paul@stripped +4 -0
  Replace some floating point language.

  refman/column-types.xml
    1.10 05/08/08 16:39:28 paul@stripped +23 -26
    Replace some floating point language.

  refman-5.1/column-types.xml
    1.2 05/08/08 16:39:28 paul@stripped +23 -26
    Sync.

  refman-5.0/column-types.xml
    1.2 05/08/08 16:39:27 paul@stripped +23 -26
    Sync.

  refman-4.1/column-types.xml
    1.10 05/08/08 16:39:27 paul@stripped +23 -26
    Sync.

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

--- 1.1/refman-5.1/column-types.xml	2005-08-05 12:46:59 -05:00
+++ 1.2/refman-5.1/column-types.xml	2005-08-08 16:39:28 -05:00
@@ -1965,35 +1965,32 @@
     </para>
 
     <para>
-      When the keyword <literal>FLOAT</literal> is used for a column
-      type without a precision specification, MySQL uses four bytes to
-      store the values. MySQL also supports variant syntax with two
-      numbers given in parentheses following the
-      <literal>FLOAT</literal> keyword. The first number represents the
-      display width and the second number specifies the number of digits
-      to be stored and displayed following the decimal point (as with
-      <literal>DECIMAL</literal> and <literal>NUMERIC</literal>).
When
-      MySQL is asked to store a number for such a column with more
-      decimal digits following the decimal point than specified for the
-      column, the value is rounded to eliminate the extra digits when
-      the value is stored.
+      MySQL allows a non-standard syntax:
+     
<literal>FLOAT(<replaceable>M</replaceable>,<replaceable>D</replaceable>)</literal>
+      or
+     
<literal>REAL(<replaceable>M</replaceable>,<replaceable>D</replaceable>)</literal>
+      or <literal>DOUBLE
+     
PRECISION(<replaceable>M</replaceable>,<replaceable>D</replaceable>)</literal>.
+      Here,
+     
<quote><literal>(<replaceable>M</replaceable>,<replaceable>D</replaceable>)</literal></quote>
+      means than values are displayed with up to
+      <replaceable>M</replaceable> decimal digits in total, of which
+      <replaceable>D</replaceable> decimal digits may be after the
+      decimal point. For example, a column defined as
+      <literal>FLOAT(7,4)</literal> will look like
+      <literal>-999.9999</literal> when displayed. MySQL performs
+      rounding when storing values, so if you insert
+      <literal>999.00009</literal> into a
<literal>FLOAT(7,4)</literal>
+      column, the approximate result is <literal>999.0001</literal>.
     </para>
 
     <para>
-      In standard SQL, the <literal>REAL</literal> and <literal>DOUBLE
-      PRECISION</literal> types do not accept precision specifications.
-      MySQL supports a variant syntax with two numbers given in
-      parentheses following the type name. The first number represents
-      the display width and the second number specifies the number of
-      digits to be stored and displayed following the decimal point. As
-      an extension to the SQL standard, MySQL recognizes
-      <literal>DOUBLE</literal> as a synonym for the <literal>DOUBLE
-      PRECISION</literal> type. In contrast with the standard's
-      requirement that the precision for <literal>REAL</literal> be
-      smaller than that used for <literal>DOUBLE PRECISION</literal>,
-      MySQL implements both as eight-byte double-precision
-      floating-point values (unless the server SQL mode includes the
-      <literal>REAL_AS_FLOAT</literal> option).
+      MySQL treats <literal>DOUBLE</literal> as a synonym for
+      <literal>DOUBLE PRECISION</literal> (a non-standard extension).
+      MySQL also treats <literal>REAL</literal> as a synonym for
+      <literal>DOUBLE PRECISION</literal> (a non-standard variation),
+      unless the server SQL mode includes the
+      <literal>REAL_AS_FLOAT</literal> option.
     </para>
 
     <para>

--- 1.9/refman-4.1/column-types.xml	2005-08-01 13:47:20 -05:00
+++ 1.10/refman-4.1/column-types.xml	2005-08-08 16:39:27 -05:00
@@ -2038,35 +2038,32 @@
     </para>
 
     <para>
-      When the keyword <literal>FLOAT</literal> is used for a column
-      type without a precision specification, MySQL uses four bytes to
-      store the values. MySQL also supports variant syntax with two
-      numbers given in parentheses following the
-      <literal>FLOAT</literal> keyword. The first number represents the
-      display width and the second number specifies the number of digits
-      to be stored and displayed following the decimal point (as with
-      <literal>DECIMAL</literal> and <literal>NUMERIC</literal>).
When
-      MySQL is asked to store a number for such a column with more
-      decimal digits following the decimal point than specified for the
-      column, the value is rounded to eliminate the extra digits when
-      the value is stored.
+      MySQL allows a non-standard syntax:
+     
<literal>FLOAT(<replaceable>M</replaceable>,<replaceable>D</replaceable>)</literal>
+      or
+     
<literal>REAL(<replaceable>M</replaceable>,<replaceable>D</replaceable>)</literal>
+      or <literal>DOUBLE
+     
PRECISION(<replaceable>M</replaceable>,<replaceable>D</replaceable>)</literal>.
+      Here,
+     
<quote><literal>(<replaceable>M</replaceable>,<replaceable>D</replaceable>)</literal></quote>
+      means than values are displayed with up to
+      <replaceable>M</replaceable> decimal digits in total, of which
+      <replaceable>D</replaceable> decimal digits may be after the
+      decimal point. For example, a column defined as
+      <literal>FLOAT(7,4)</literal> will look like
+      <literal>-999.9999</literal> when displayed. MySQL performs
+      rounding when storing values, so if you insert
+      <literal>999.00009</literal> into a
<literal>FLOAT(7,4)</literal>
+      column, the approximate result is <literal>999.0001</literal>.
     </para>
 
     <para>
-      In standard SQL, the <literal>REAL</literal> and <literal>DOUBLE
-      PRECISION</literal> types do not accept precision specifications.
-      MySQL supports a variant syntax with two numbers given in
-      parentheses following the type name. The first number represents
-      the display width and the second number specifies the number of
-      digits to be stored and displayed following the decimal point. As
-      an extension to the SQL standard, MySQL recognizes
-      <literal>DOUBLE</literal> as a synonym for the <literal>DOUBLE
-      PRECISION</literal> type. In contrast with the standard's
-      requirement that the precision for <literal>REAL</literal> be
-      smaller than that used for <literal>DOUBLE PRECISION</literal>,
-      MySQL implements both as eight-byte double-precision
-      floating-point values (unless the server SQL mode includes the
-      <literal>REAL_AS_FLOAT</literal> option).
+      MySQL treats <literal>DOUBLE</literal> as a synonym for
+      <literal>DOUBLE PRECISION</literal> (a non-standard extension).
+      MySQL also treats <literal>REAL</literal> as a synonym for
+      <literal>DOUBLE PRECISION</literal> (a non-standard variation),
+      unless the server SQL mode includes the
+      <literal>REAL_AS_FLOAT</literal> option.
     </para>
 
     <para>

--- 1.9/refman/column-types.xml	2005-08-01 13:47:21 -05:00
+++ 1.10/refman/column-types.xml	2005-08-08 16:39:28 -05:00
@@ -2038,35 +2038,32 @@
     </para>
 
     <para>
-      When the keyword <literal>FLOAT</literal> is used for a column
-      type without a precision specification, MySQL uses four bytes to
-      store the values. MySQL also supports variant syntax with two
-      numbers given in parentheses following the
-      <literal>FLOAT</literal> keyword. The first number represents the
-      display width and the second number specifies the number of digits
-      to be stored and displayed following the decimal point (as with
-      <literal>DECIMAL</literal> and <literal>NUMERIC</literal>).
When
-      MySQL is asked to store a number for such a column with more
-      decimal digits following the decimal point than specified for the
-      column, the value is rounded to eliminate the extra digits when
-      the value is stored.
+      MySQL allows a non-standard syntax:
+     
<literal>FLOAT(<replaceable>M</replaceable>,<replaceable>D</replaceable>)</literal>
+      or
+     
<literal>REAL(<replaceable>M</replaceable>,<replaceable>D</replaceable>)</literal>
+      or <literal>DOUBLE
+     
PRECISION(<replaceable>M</replaceable>,<replaceable>D</replaceable>)</literal>.
+      Here,
+     
<quote><literal>(<replaceable>M</replaceable>,<replaceable>D</replaceable>)</literal></quote>
+      means than values are displayed with up to
+      <replaceable>M</replaceable> decimal digits in total, of which
+      <replaceable>D</replaceable> decimal digits may be after the
+      decimal point. For example, a column defined as
+      <literal>FLOAT(7,4)</literal> will look like
+      <literal>-999.9999</literal> when displayed. MySQL performs
+      rounding when storing values, so if you insert
+      <literal>999.00009</literal> into a
<literal>FLOAT(7,4)</literal>
+      column, the approximate result is <literal>999.0001</literal>.
     </para>
 
     <para>
-      In standard SQL, the <literal>REAL</literal> and <literal>DOUBLE
-      PRECISION</literal> types do not accept precision specifications.
-      MySQL supports a variant syntax with two numbers given in
-      parentheses following the type name. The first number represents
-      the display width and the second number specifies the number of
-      digits to be stored and displayed following the decimal point. As
-      an extension to the SQL standard, MySQL recognizes
-      <literal>DOUBLE</literal> as a synonym for the <literal>DOUBLE
-      PRECISION</literal> type. In contrast with the standard's
-      requirement that the precision for <literal>REAL</literal> be
-      smaller than that used for <literal>DOUBLE PRECISION</literal>,
-      MySQL implements both as eight-byte double-precision
-      floating-point values (unless the server SQL mode includes the
-      <literal>REAL_AS_FLOAT</literal> option).
+      MySQL treats <literal>DOUBLE</literal> as a synonym for
+      <literal>DOUBLE PRECISION</literal> (a non-standard extension).
+      MySQL also treats <literal>REAL</literal> as a synonym for
+      <literal>DOUBLE PRECISION</literal> (a non-standard variation),
+      unless the server SQL mode includes the
+      <literal>REAL_AS_FLOAT</literal> option.
     </para>
 
     <para>

--- 1.1/refman-5.0/column-types.xml	2005-08-05 12:11:25 -05:00
+++ 1.2/refman-5.0/column-types.xml	2005-08-08 16:39:27 -05:00
@@ -1965,35 +1965,32 @@
     </para>
 
     <para>
-      When the keyword <literal>FLOAT</literal> is used for a column
-      type without a precision specification, MySQL uses four bytes to
-      store the values. MySQL also supports variant syntax with two
-      numbers given in parentheses following the
-      <literal>FLOAT</literal> keyword. The first number represents the
-      display width and the second number specifies the number of digits
-      to be stored and displayed following the decimal point (as with
-      <literal>DECIMAL</literal> and <literal>NUMERIC</literal>).
When
-      MySQL is asked to store a number for such a column with more
-      decimal digits following the decimal point than specified for the
-      column, the value is rounded to eliminate the extra digits when
-      the value is stored.
+      MySQL allows a non-standard syntax:
+     
<literal>FLOAT(<replaceable>M</replaceable>,<replaceable>D</replaceable>)</literal>
+      or
+     
<literal>REAL(<replaceable>M</replaceable>,<replaceable>D</replaceable>)</literal>
+      or <literal>DOUBLE
+     
PRECISION(<replaceable>M</replaceable>,<replaceable>D</replaceable>)</literal>.
+      Here,
+     
<quote><literal>(<replaceable>M</replaceable>,<replaceable>D</replaceable>)</literal></quote>
+      means than values are displayed with up to
+      <replaceable>M</replaceable> decimal digits in total, of which
+      <replaceable>D</replaceable> decimal digits may be after the
+      decimal point. For example, a column defined as
+      <literal>FLOAT(7,4)</literal> will look like
+      <literal>-999.9999</literal> when displayed. MySQL performs
+      rounding when storing values, so if you insert
+      <literal>999.00009</literal> into a
<literal>FLOAT(7,4)</literal>
+      column, the approximate result is <literal>999.0001</literal>.
     </para>
 
     <para>
-      In standard SQL, the <literal>REAL</literal> and <literal>DOUBLE
-      PRECISION</literal> types do not accept precision specifications.
-      MySQL supports a variant syntax with two numbers given in
-      parentheses following the type name. The first number represents
-      the display width and the second number specifies the number of
-      digits to be stored and displayed following the decimal point. As
-      an extension to the SQL standard, MySQL recognizes
-      <literal>DOUBLE</literal> as a synonym for the <literal>DOUBLE
-      PRECISION</literal> type. In contrast with the standard's
-      requirement that the precision for <literal>REAL</literal> be
-      smaller than that used for <literal>DOUBLE PRECISION</literal>,
-      MySQL implements both as eight-byte double-precision
-      floating-point values (unless the server SQL mode includes the
-      <literal>REAL_AS_FLOAT</literal> option).
+      MySQL treats <literal>DOUBLE</literal> as a synonym for
+      <literal>DOUBLE PRECISION</literal> (a non-standard extension).
+      MySQL also treats <literal>REAL</literal> as a synonym for
+      <literal>DOUBLE PRECISION</literal> (a non-standard variation),
+      unless the server SQL mode includes the
+      <literal>REAL_AS_FLOAT</literal> option.
     </para>
 
     <para>