List:Commits« Previous MessageNext Message »
From:paul.dubois Date:October 7 2010 2:57pm
Subject:svn commit - mysqldoc@docsrva: r23046 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-5.5 refman-5.6 refman-6.0
View as plain text  
Author: paul
Date: 2010-10-07 16:57:36 +0200 (Thu, 07 Oct 2010)
New Revision: 23046

Log:
 r63931@frost:  paul | 2010-10-07 09:55:48 -0500
 Some numeric-types revisions


Modified:
   trunk/refman-4.1/data-types.xml
   trunk/refman-5.0/data-types.xml
   trunk/refman-5.1/data-types.xml
   trunk/refman-5.5/data-types.xml
   trunk/refman-5.6/data-types.xml
   trunk/refman-6.0/data-types.xml

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:35498
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:42900
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:63925
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546
   + 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:35498
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:42900
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:63931
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546


Modified: trunk/refman-4.1/data-types.xml
===================================================================
--- trunk/refman-4.1/data-types.xml	2010-10-07 14:20:48 UTC (rev 23045)
+++ trunk/refman-4.1/data-types.xml	2010-10-07 14:57:36 UTC (rev 23046)
Changed blocks: 10, Lines Added: 29, Lines Deleted: 30; 5995 bytes

@@ -2291,9 +2291,9 @@
     </para>
 
     <para>
-      The type used for the result of a calculation on numeric operands
-      depends on the types of the operands and the operations performed
-      on them. For more information, see
+      The data type used for the result of a calculation on numeric
+      operands depends on the types of the operands and the operations
+      performed on them. For more information, see
       <xref linkend="arithmetic-functions"/>.
     </para>
 

@@ -2308,7 +2308,7 @@
       <literal role="type">TINYINT</literal>,
       <literal role="type">MEDIUMINT</literal>, and
       <literal role="type">BIGINT</literal>. The following table shows
-      the required storage and range for each of the integer types.
+      the required storage and range for each integer type.
     </para>
 
     <informaltable>

@@ -2488,17 +2488,14 @@
       <literal>2</literal> is the scale. The precision represents the
       number of significant digits that are stored for values, and the
       scale represents the number of digits that can be stored following
-      the decimal point. If the scale is 0,
-      <literal role="type">DECIMAL</literal> values contain no decimal
-      point or fractional part.
+      the decimal point.
     </para>
 
     <para>
-      Standard SQL requires that the <literal>salary</literal> column be
-      able to store any value with five digits and two decimals. In this
-      case, therefore, the range of values that can be stored in the
-      <literal>salary</literal> column is from
-      <literal>-999.99</literal> to <literal>999.99</literal>. In
+      Standard SQL requires that <literal>DECIMAL(5,2)</literal> be able
+      to store any value with five digits and two decimals, so values
+      that can be stored in the <literal>salary</literal> column range
+      from <literal>-999.99</literal> to <literal>999.99</literal>. In
       versions up to and including 4.1, MySQL varies from this limit in
       two ways due to the use of string format for value storage:
     </para>

@@ -2529,8 +2526,6 @@
 
     </itemizedlist>
 
-    <bridgehead>Bit-Value Type</bridgehead>
-
     <para>
       In standard SQL, the syntax
       <literal>DECIMAL(<replaceable>M</replaceable>)</literal> is

@@ -2548,6 +2543,11 @@
     </para>
 
     <para>
+      If the scale is 0, <literal role="type">DECIMAL</literal> values
+      contain no decimal point or fractional part.
+    </para>
+
+    <para>
       The maximum range of <literal role="type">DECIMAL</literal> values
       is the same as for <literal role="type">DOUBLE</literal>, but the
       actual range for a given <literal role="type">DECIMAL</literal>

@@ -2562,17 +2562,16 @@
     <bridgehead>Numeric Type Attributes</bridgehead>
 
     <para>
-      MySQL supports and extension for optionally specifying the display
+      MySQL supports an extension for optionally specifying the display
       width of integer data types in parentheses following the base
       keyword for the type. For example,
       <literal role="type">INT(4)</literal> specifies an
-      <literal role="type">INT</literal> with a display with of four
-      characters. This optional display width may be used by
-      applications to display integer values having a width less than
-      the width specified for the column by left-padding them with
-      spaces. (That is, this width is present in the metadata returned
-      with result sets. Whether it is used or not is up to the
-      application.)
+      <literal role="type">INT</literal> with a display width of four
+      digits. This optional display width may be used by applications to
+      display integer values having a width less than the width
+      specified for the column by left-padding them with spaces. (That
+      is, this width is present in the metadata returned with result
+      sets. Whether it is used or not is up to the application.)
     </para>
 
     <para>

@@ -2583,8 +2582,8 @@
       <literal role="type">SMALLINT(3)</literal> has the usual
       <literal role="type">SMALLINT</literal> range of
       <literal>-32768</literal> to <literal>32767</literal>, and values
-      outside the range permitted by three characters are displayed
-      using more than three characters.
+      outside the range permitted by three digits are displayed in full
+      using more than three digits.
     </para>
 
     <para>

@@ -2613,9 +2612,9 @@
 
     <para>
       All integer types can have an optional (nonstandard) attribute
-      <literal>UNSIGNED</literal>. Unsigned values can be used when you
-      want to permit only nonnegative numbers in a column or you need a
-      larger upper numeric range for the column. For example, if an
+      <literal>UNSIGNED</literal>. Unsigned type can be used to permit
+      only nonnegative numbers in a column or when you need a larger
+      upper numeric range for the column. For example, if an
       <literal role="type">INT</literal> column is
       <literal>UNSIGNED</literal>, the size of the column's range is the
       same but its endpoints shift from <literal>-2147483648</literal>

@@ -3884,7 +3883,7 @@
               one, or neither. (For example, you can specify <literal>ON
               UPDATE</literal> to enable auto-update without also having
               the column auto-initialized.) The following column
-              definitions demonstrate each of the possibilities:
+              definitions demonstrate each possibility:
             </para>
 
             <itemizedlist>

@@ -5907,8 +5906,8 @@
     </indexterm>
 
     <para>
-      The storage requirements for each of the data types supported by
-      MySQL are listed here by category.
+      The storage requirements for each data type supported by MySQL are
+      listed here by category.
     </para>
 
     <indexterm>


Modified: trunk/refman-5.0/data-types.xml
===================================================================
--- trunk/refman-5.0/data-types.xml	2010-10-07 14:20:48 UTC (rev 23045)
+++ trunk/refman-5.0/data-types.xml	2010-10-07 14:57:36 UTC (rev 23046)
Changed blocks: 9, Lines Added: 31, Lines Deleted: 30; 6203 bytes

@@ -2401,9 +2401,9 @@
     </para>
 
     <para>
-      The type used for the result of a calculation on numeric operands
-      depends on the types of the operands and the operations performed
-      on them. For more information, see
+      The data type used for the result of a calculation on numeric
+      operands depends on the types of the operands and the operations
+      performed on them. For more information, see
       <xref linkend="arithmetic-functions"/>.
     </para>
 

@@ -2418,7 +2418,7 @@
       <literal role="type">TINYINT</literal>,
       <literal role="type">MEDIUMINT</literal>, and
       <literal role="type">BIGINT</literal>. The following table shows
-      the required storage and range for each of the integer types.
+      the required storage and range for each integer type.
     </para>
 
     <informaltable>

@@ -2599,18 +2599,15 @@
       <literal>2</literal> is the scale. The precision represents the
       number of significant digits that are stored for values, and the
       scale represents the number of digits that can be stored following
-      the decimal point. If the scale is 0,
-      <literal role="type">DECIMAL</literal> values contain no decimal
-      point or fractional part.
+      the decimal point.
     </para>
 
     <para>
-      Standard SQL requires that the <literal>salary</literal> column be
-      able to store any value with five digits and two decimals. In this
-      case, therefore, the range of values that can be stored in the
-      <literal>salary</literal> column is from
-      <literal>-999.99</literal> to <literal>999.99</literal>. MySQL
-      enforces this limit as of MySQL 5.0.3. Before 5.0.3, on the
+      Standard SQL requires that <literal>DECIMAL(5,2)</literal> be able
+      to store any value with five digits and two decimals, so values
+      that can be stored in the <literal>salary</literal> column range
+      from <literal>-999.99</literal> to <literal>999.99</literal>.
+      MySQL enforces this limit as of MySQL 5.0.3. Before 5.0.3, on the
       positive end of the range, the column could actually store numbers
       up to <literal>9999.99</literal>. (For positive numbers, MySQL
       5.0.2 and earlier used the byte reserved for the sign to extend

@@ -2631,6 +2628,11 @@
       default value of <replaceable>M</replaceable> is 10.
     </para>
 
+    <para>
+      If the scale is 0, <literal role="type">DECIMAL</literal> values
+      contain no decimal point or fractional part.
+    </para>
+
     <bridgehead>Bit-Value Type</bridgehead>
 
     <para>

@@ -2678,17 +2680,16 @@
     <bridgehead>Numeric Type Attributes</bridgehead>
 
     <para>
-      MySQL supports and extension for optionally specifying the display
+      MySQL supports an extension for optionally specifying the display
       width of integer data types in parentheses following the base
       keyword for the type. For example,
       <literal role="type">INT(4)</literal> specifies an
-      <literal role="type">INT</literal> with a display with of four
-      characters. This optional display width may be used by
-      applications to display integer values having a width less than
-      the width specified for the column by left-padding them with
-      spaces. (That is, this width is present in the metadata returned
-      with result sets. Whether it is used or not is up to the
-      application.)
+      <literal role="type">INT</literal> with a display width of four
+      digits. This optional display width may be used by applications to
+      display integer values having a width less than the width
+      specified for the column by left-padding them with spaces. (That
+      is, this width is present in the metadata returned with result
+      sets. Whether it is used or not is up to the application.)
     </para>
 
     <para>

@@ -2699,8 +2700,8 @@
       <literal role="type">SMALLINT(3)</literal> has the usual
       <literal role="type">SMALLINT</literal> range of
       <literal>-32768</literal> to <literal>32767</literal>, and values
-      outside the range permitted by three characters are displayed
-      using more than three characters.
+      outside the range permitted by three digits are displayed in full
+      using more than three digits.
     </para>
 
     <para>

@@ -2729,9 +2730,9 @@
 
     <para>
       All integer types can have an optional (nonstandard) attribute
-      <literal>UNSIGNED</literal>. Unsigned values can be used when you
-      want to permit only nonnegative numbers in a column or you need a
-      larger upper numeric range for the column. For example, if an
+      <literal>UNSIGNED</literal>. Unsigned type can be used to permit
+      only nonnegative numbers in a column or when you need a larger
+      upper numeric range for the column. For example, if an
       <literal role="type">INT</literal> column is
       <literal>UNSIGNED</literal>, the size of the column's range is the
       same but its endpoints shift from <literal>-2147483648</literal>

@@ -3649,7 +3650,7 @@
               one, or neither. (For example, you can specify <literal>ON
               UPDATE</literal> to enable auto-update without also having
               the column auto-initialized.) The following column
-              definitions demonstrate each of the possibilities:
+              definitions demonstrate each possibility:
             </para>
 
             <itemizedlist>

@@ -5742,9 +5743,9 @@
 
     <para>
       This sections includes some guideliness and information for the
-      the storage requirements for each of the data types supported by
-      MySQL, including details for the internal format and the sizes
-      used by storage engines that used a fixed size representation for
+      the storage requirements for each data type supported by MySQL,
+      including details for the internal format and the sizes used by
+      storage engines that used a fixed size representation for
       different types. Information is listed by category or storage
       engine.
     </para>


Modified: trunk/refman-5.1/data-types.xml
===================================================================
--- trunk/refman-5.1/data-types.xml	2010-10-07 14:20:48 UTC (rev 23045)
+++ trunk/refman-5.1/data-types.xml	2010-10-07 14:57:36 UTC (rev 23046)
Changed blocks: 9, Lines Added: 30, Lines Deleted: 29; 5950 bytes

@@ -2256,9 +2256,9 @@
     </para>
 
     <para>
-      The type used for the result of a calculation on numeric operands
-      depends on the types of the operands and the operations performed
-      on them. For more information, see
+      The data type used for the result of a calculation on numeric
+      operands depends on the types of the operands and the operations
+      performed on them. For more information, see
       <xref linkend="arithmetic-functions"/>.
     </para>
 

@@ -2273,7 +2273,7 @@
       <literal role="type">TINYINT</literal>,
       <literal role="type">MEDIUMINT</literal>, and
       <literal role="type">BIGINT</literal>. The following table shows
-      the required storage and range for each of the integer types.
+      the required storage and range for each integer type.
     </para>
 
     <informaltable>

@@ -2452,17 +2452,14 @@
       <literal>2</literal> is the scale. The precision represents the
       number of significant digits that are stored for values, and the
       scale represents the number of digits that can be stored following
-      the decimal point. If the scale is 0,
-      <literal role="type">DECIMAL</literal> values contain no decimal
-      point or fractional part.
+      the decimal point.
     </para>
 
     <para>
-      Standard SQL requires that the <literal>salary</literal> column be
-      able to store any value with five digits and two decimals. In this
-      case, therefore, the range of values that can be stored in the
-      <literal>salary</literal> column is from
-      <literal>-999.99</literal> to <literal>999.99</literal>.
+      Standard SQL requires that <literal>DECIMAL(5,2)</literal> be able
+      to store any value with five digits and two decimals, so values
+      that can be stored in the <literal>salary</literal> column range
+      from <literal>-999.99</literal> to <literal>999.99</literal>.
     </para>
 
     <para>

@@ -2480,6 +2477,11 @@
     </para>
 
     <para>
+      If the scale is 0, <literal role="type">DECIMAL</literal> values
+      contain no decimal point or fractional part.
+    </para>
+
+    <para>
       The maximum number of digits for
       <literal role="type">DECIMAL</literal> is 65, but the actual range
       for a given <literal role="type">DECIMAL</literal> column can be

@@ -2523,17 +2525,16 @@
     <bridgehead>Numeric Type Attributes</bridgehead>
 
     <para>
-      MySQL supports and extension for optionally specifying the display
+      MySQL supports an extension for optionally specifying the display
       width of integer data types in parentheses following the base
       keyword for the type. For example,
       <literal role="type">INT(4)</literal> specifies an
-      <literal role="type">INT</literal> with a display with of four
-      characters. This optional display width may be used by
-      applications to display integer values having a width less than
-      the width specified for the column by left-padding them with
-      spaces. (That is, this width is present in the metadata returned
-      with result sets. Whether it is used or not is up to the
-      application.)
+      <literal role="type">INT</literal> with a display width of four
+      digits. This optional display width may be used by applications to
+      display integer values having a width less than the width
+      specified for the column by left-padding them with spaces. (That
+      is, this width is present in the metadata returned with result
+      sets. Whether it is used or not is up to the application.)
     </para>
 
     <para>

@@ -2544,8 +2545,8 @@
       <literal role="type">SMALLINT(3)</literal> has the usual
       <literal role="type">SMALLINT</literal> range of
       <literal>-32768</literal> to <literal>32767</literal>, and values
-      outside the range permitted by three characters are displayed
-      using more than three characters.
+      outside the range permitted by three digits are displayed in full
+      using more than three digits.
     </para>
 
     <para>

@@ -2574,9 +2575,9 @@
 
     <para>
       All integer types can have an optional (nonstandard) attribute
-      <literal>UNSIGNED</literal>. Unsigned values can be used when you
-      want to permit only nonnegative numbers in a column or you need a
-      larger upper numeric range for the column. For example, if an
+      <literal>UNSIGNED</literal>. Unsigned type can be used to permit
+      only nonnegative numbers in a column or when you need a larger
+      upper numeric range for the column. For example, if an
       <literal role="type">INT</literal> column is
       <literal>UNSIGNED</literal>, the size of the column's range is the
       same but its endpoints shift from <literal>-2147483648</literal>

@@ -3463,7 +3464,7 @@
               one, or neither. (For example, you can specify <literal>ON
               UPDATE</literal> to enable auto-update without also having
               the column auto-initialized.) The following column
-              definitions demonstrate each of the possibilities:
+              definitions demonstrate each possibility:
             </para>
 
             <itemizedlist>

@@ -5469,9 +5470,9 @@
 
     <para>
       This sections includes some guideliness and information for the
-      the storage requirements for each of the data types supported by
-      MySQL, including details for the internal format and the sizes
-      used by storage engines that used a fixed size representation for
+      the storage requirements for each data type supported by MySQL,
+      including details for the internal format and the sizes used by
+      storage engines that used a fixed size representation for
       different types. Information is listed by category or storage
       engine.
     </para>


Modified: trunk/refman-5.5/data-types.xml
===================================================================
--- trunk/refman-5.5/data-types.xml	2010-10-07 14:20:48 UTC (rev 23045)
+++ trunk/refman-5.5/data-types.xml	2010-10-07 14:57:36 UTC (rev 23046)
Changed blocks: 9, Lines Added: 30, Lines Deleted: 29; 5950 bytes

@@ -2256,9 +2256,9 @@
     </para>
 
     <para>
-      The type used for the result of a calculation on numeric operands
-      depends on the types of the operands and the operations performed
-      on them. For more information, see
+      The data type used for the result of a calculation on numeric
+      operands depends on the types of the operands and the operations
+      performed on them. For more information, see
       <xref linkend="arithmetic-functions"/>.
     </para>
 

@@ -2273,7 +2273,7 @@
       <literal role="type">TINYINT</literal>,
       <literal role="type">MEDIUMINT</literal>, and
       <literal role="type">BIGINT</literal>. The following table shows
-      the required storage and range for each of the integer types.
+      the required storage and range for each integer type.
     </para>
 
     <informaltable>

@@ -2451,17 +2451,14 @@
       <literal>2</literal> is the scale. The precision represents the
       number of significant digits that are stored for values, and the
       scale represents the number of digits that can be stored following
-      the decimal point. If the scale is 0,
-      <literal role="type">DECIMAL</literal> values contain no decimal
-      point or fractional part.
+      the decimal point.
     </para>
 
     <para>
-      Standard SQL requires that the <literal>salary</literal> column be
-      able to store any value with five digits and two decimals. In this
-      case, therefore, the range of values that can be stored in the
-      <literal>salary</literal> column is from
-      <literal>-999.99</literal> to <literal>999.99</literal>.
+      Standard SQL requires that <literal>DECIMAL(5,2)</literal> be able
+      to store any value with five digits and two decimals, so values
+      that can be stored in the <literal>salary</literal> column range
+      from <literal>-999.99</literal> to <literal>999.99</literal>.
     </para>
 
     <para>

@@ -2479,6 +2476,11 @@
     </para>
 
     <para>
+      If the scale is 0, <literal role="type">DECIMAL</literal> values
+      contain no decimal point or fractional part.
+    </para>
+
+    <para>
       The maximum number of digits for
       <literal role="type">DECIMAL</literal> is 65, but the actual range
       for a given <literal role="type">DECIMAL</literal> column can be

@@ -2522,17 +2524,16 @@
     <bridgehead>Numeric Type Attributes</bridgehead>
 
     <para>
-      MySQL supports and extension for optionally specifying the display
+      MySQL supports an extension for optionally specifying the display
       width of integer data types in parentheses following the base
       keyword for the type. For example,
       <literal role="type">INT(4)</literal> specifies an
-      <literal role="type">INT</literal> with a display with of four
-      characters. This optional display width may be used by
-      applications to display integer values having a width less than
-      the width specified for the column by left-padding them with
-      spaces. (That is, this width is present in the metadata returned
-      with result sets. Whether it is used or not is up to the
-      application.)
+      <literal role="type">INT</literal> with a display width of four
+      digits. This optional display width may be used by applications to
+      display integer values having a width less than the width
+      specified for the column by left-padding them with spaces. (That
+      is, this width is present in the metadata returned with result
+      sets. Whether it is used or not is up to the application.)
     </para>
 
     <para>

@@ -2543,8 +2544,8 @@
       <literal role="type">SMALLINT(3)</literal> has the usual
       <literal role="type">SMALLINT</literal> range of
       <literal>-32768</literal> to <literal>32767</literal>, and values
-      outside the range permitted by three characters are displayed
-      using more than three characters.
+      outside the range permitted by three digits are displayed in full
+      using more than three digits.
     </para>
 
     <para>

@@ -2573,9 +2574,9 @@
 
     <para>
       All integer types can have an optional (nonstandard) attribute
-      <literal>UNSIGNED</literal>. Unsigned values can be used when you
-      want to permit only nonnegative numbers in a column or you need a
-      larger upper numeric range for the column. For example, if an
+      <literal>UNSIGNED</literal>. Unsigned type can be used to permit
+      only nonnegative numbers in a column or when you need a larger
+      upper numeric range for the column. For example, if an
       <literal role="type">INT</literal> column is
       <literal>UNSIGNED</literal>, the size of the column's range is the
       same but its endpoints shift from <literal>-2147483648</literal>

@@ -3476,7 +3477,7 @@
               one, or neither. (For example, you can specify <literal>ON
               UPDATE</literal> to enable auto-update without also having
               the column auto-initialized.) The following column
-              definitions demonstrate each of the possibilities:
+              definitions demonstrate each possibility:
             </para>
 
             <itemizedlist>

@@ -5481,9 +5482,9 @@
 
     <para>
       This sections includes some guideliness and information for the
-      the storage requirements for each of the data types supported by
-      MySQL, including details for the internal format and the sizes
-      used by storage engines that used a fixed size representation for
+      the storage requirements for each data type supported by MySQL,
+      including details for the internal format and the sizes used by
+      storage engines that used a fixed size representation for
       different types. Information is listed by category or storage
       engine.
     </para>


Modified: trunk/refman-5.6/data-types.xml
===================================================================
--- trunk/refman-5.6/data-types.xml	2010-10-07 14:20:48 UTC (rev 23045)
+++ trunk/refman-5.6/data-types.xml	2010-10-07 14:57:36 UTC (rev 23046)
Changed blocks: 9, Lines Added: 30, Lines Deleted: 29; 5950 bytes

@@ -2256,9 +2256,9 @@
     </para>
 
     <para>
-      The type used for the result of a calculation on numeric operands
-      depends on the types of the operands and the operations performed
-      on them. For more information, see
+      The data type used for the result of a calculation on numeric
+      operands depends on the types of the operands and the operations
+      performed on them. For more information, see
       <xref linkend="arithmetic-functions"/>.
     </para>
 

@@ -2273,7 +2273,7 @@
       <literal role="type">TINYINT</literal>,
       <literal role="type">MEDIUMINT</literal>, and
       <literal role="type">BIGINT</literal>. The following table shows
-      the required storage and range for each of the integer types.
+      the required storage and range for each integer type.
     </para>
 
     <informaltable>

@@ -2451,17 +2451,14 @@
       <literal>2</literal> is the scale. The precision represents the
       number of significant digits that are stored for values, and the
       scale represents the number of digits that can be stored following
-      the decimal point. If the scale is 0,
-      <literal role="type">DECIMAL</literal> values contain no decimal
-      point or fractional part.
+      the decimal point.
     </para>
 
     <para>
-      Standard SQL requires that the <literal>salary</literal> column be
-      able to store any value with five digits and two decimals. In this
-      case, therefore, the range of values that can be stored in the
-      <literal>salary</literal> column is from
-      <literal>-999.99</literal> to <literal>999.99</literal>.
+      Standard SQL requires that <literal>DECIMAL(5,2)</literal> be able
+      to store any value with five digits and two decimals, so values
+      that can be stored in the <literal>salary</literal> column range
+      from <literal>-999.99</literal> to <literal>999.99</literal>.
     </para>
 
     <para>

@@ -2479,6 +2476,11 @@
     </para>
 
     <para>
+      If the scale is 0, <literal role="type">DECIMAL</literal> values
+      contain no decimal point or fractional part.
+    </para>
+
+    <para>
       The maximum number of digits for
       <literal role="type">DECIMAL</literal> is 65, but the actual range
       for a given <literal role="type">DECIMAL</literal> column can be

@@ -2522,17 +2524,16 @@
     <bridgehead>Numeric Type Attributes</bridgehead>
 
     <para>
-      MySQL supports and extension for optionally specifying the display
+      MySQL supports an extension for optionally specifying the display
       width of integer data types in parentheses following the base
       keyword for the type. For example,
       <literal role="type">INT(4)</literal> specifies an
-      <literal role="type">INT</literal> with a display with of four
-      characters. This optional display width may be used by
-      applications to display integer values having a width less than
-      the width specified for the column by left-padding them with
-      spaces. (That is, this width is present in the metadata returned
-      with result sets. Whether it is used or not is up to the
-      application.)
+      <literal role="type">INT</literal> with a display width of four
+      digits. This optional display width may be used by applications to
+      display integer values having a width less than the width
+      specified for the column by left-padding them with spaces. (That
+      is, this width is present in the metadata returned with result
+      sets. Whether it is used or not is up to the application.)
     </para>
 
     <para>

@@ -2543,8 +2544,8 @@
       <literal role="type">SMALLINT(3)</literal> has the usual
       <literal role="type">SMALLINT</literal> range of
       <literal>-32768</literal> to <literal>32767</literal>, and values
-      outside the range permitted by three characters are displayed
-      using more than three characters.
+      outside the range permitted by three digits are displayed in full
+      using more than three digits.
     </para>
 
     <para>

@@ -2573,9 +2574,9 @@
 
     <para>
       All integer types can have an optional (nonstandard) attribute
-      <literal>UNSIGNED</literal>. Unsigned values can be used when you
-      want to permit only nonnegative numbers in a column or you need a
-      larger upper numeric range for the column. For example, if an
+      <literal>UNSIGNED</literal>. Unsigned type can be used to permit
+      only nonnegative numbers in a column or when you need a larger
+      upper numeric range for the column. For example, if an
       <literal role="type">INT</literal> column is
       <literal>UNSIGNED</literal>, the size of the column's range is the
       same but its endpoints shift from <literal>-2147483648</literal>

@@ -3476,7 +3477,7 @@
               one, or neither. (For example, you can specify <literal>ON
               UPDATE</literal> to enable auto-update without also having
               the column auto-initialized.) The following column
-              definitions demonstrate each of the possibilities:
+              definitions demonstrate each possibility:
             </para>
 
             <itemizedlist>

@@ -5481,9 +5482,9 @@
 
     <para>
       This sections includes some guideliness and information for the
-      the storage requirements for each of the data types supported by
-      MySQL, including details for the internal format and the sizes
-      used by storage engines that used a fixed size representation for
+      the storage requirements for each data type supported by MySQL,
+      including details for the internal format and the sizes used by
+      storage engines that used a fixed size representation for
       different types. Information is listed by category or storage
       engine.
     </para>


Modified: trunk/refman-6.0/data-types.xml
===================================================================
--- trunk/refman-6.0/data-types.xml	2010-10-07 14:20:48 UTC (rev 23045)
+++ trunk/refman-6.0/data-types.xml	2010-10-07 14:57:36 UTC (rev 23046)
Changed blocks: 9, Lines Added: 29, Lines Deleted: 28; 5632 bytes

@@ -2256,9 +2256,9 @@
     </para>
 
     <para>
-      The type used for the result of a calculation on numeric operands
-      depends on the types of the operands and the operations performed
-      on them. For more information, see
+      The data type used for the result of a calculation on numeric
+      operands depends on the types of the operands and the operations
+      performed on them. For more information, see
       <xref linkend="arithmetic-functions"/>.
     </para>
 

@@ -2273,7 +2273,7 @@
       <literal role="type">TINYINT</literal>,
       <literal role="type">MEDIUMINT</literal>, and
       <literal role="type">BIGINT</literal>. The following table shows
-      the required storage and range for each of the integer types.
+      the required storage and range for each integer type.
     </para>
 
     <informaltable>

@@ -2451,17 +2451,14 @@
       <literal>2</literal> is the scale. The precision represents the
       number of significant digits that are stored for values, and the
       scale represents the number of digits that can be stored following
-      the decimal point. If the scale is 0,
-      <literal role="type">DECIMAL</literal> values contain no decimal
-      point or fractional part.
+      the decimal point.
     </para>
 
     <para>
-      Standard SQL requires that the <literal>salary</literal> column be
-      able to store any value with five digits and two decimals. In this
-      case, therefore, the range of values that can be stored in the
-      <literal>salary</literal> column is from
-      <literal>-999.99</literal> to <literal>999.99</literal>.
+      Standard SQL requires that <literal>DECIMAL(5,2)</literal> be able
+      to store any value with five digits and two decimals, so values
+      that can be stored in the <literal>salary</literal> column range
+      from <literal>-999.99</literal> to <literal>999.99</literal>.
     </para>
 
     <para>

@@ -2479,6 +2476,11 @@
     </para>
 
     <para>
+      If the scale is 0, <literal role="type">DECIMAL</literal> values
+      contain no decimal point or fractional part.
+    </para>
+
+    <para>
       The maximum number of digits for
       <literal role="type">DECIMAL</literal> is 65, but the actual range
       for a given <literal role="type">DECIMAL</literal> column can be

@@ -2522,17 +2524,16 @@
     <bridgehead>Numeric Type Attributes</bridgehead>
 
     <para>
-      MySQL supports and extension for optionally specifying the display
+      MySQL supports an extension for optionally specifying the display
       width of integer data types in parentheses following the base
       keyword for the type. For example,
       <literal role="type">INT(4)</literal> specifies an
-      <literal role="type">INT</literal> with a display with of four
-      characters. This optional display width may be used by
-      applications to display integer values having a width less than
-      the width specified for the column by left-padding them with
-      spaces. (That is, this width is present in the metadata returned
-      with result sets. Whether it is used or not is up to the
-      application.)
+      <literal role="type">INT</literal> with a display width of four
+      digits. This optional display width may be used by applications to
+      display integer values having a width less than the width
+      specified for the column by left-padding them with spaces. (That
+      is, this width is present in the metadata returned with result
+      sets. Whether it is used or not is up to the application.)
     </para>
 
     <para>

@@ -2543,8 +2544,8 @@
       <literal role="type">SMALLINT(3)</literal> has the usual
       <literal role="type">SMALLINT</literal> range of
       <literal>-32768</literal> to <literal>32767</literal>, and values
-      outside the range permitted by three characters are displayed
-      using more than three characters.
+      outside the range permitted by three digits are displayed in full
+      using more than three digits.
     </para>
 
     <para>

@@ -2573,9 +2574,9 @@
 
     <para>
       All integer types can have an optional (nonstandard) attribute
-      <literal>UNSIGNED</literal>. Unsigned values can be used when you
-      want to permit only nonnegative numbers in a column or you need a
-      larger upper numeric range for the column. For example, if an
+      <literal>UNSIGNED</literal>. Unsigned type can be used to permit
+      only nonnegative numbers in a column or when you need a larger
+      upper numeric range for the column. For example, if an
       <literal role="type">INT</literal> column is
       <literal>UNSIGNED</literal>, the size of the column's range is the
       same but its endpoints shift from <literal>-2147483648</literal>

@@ -3476,7 +3477,7 @@
               one, or neither. (For example, you can specify <literal>ON
               UPDATE</literal> to enable auto-update without also having
               the column auto-initialized.) The following column
-              definitions demonstrate each of the possibilities:
+              definitions demonstrate each possibility:
             </para>
 
             <itemizedlist>

@@ -5464,8 +5465,8 @@
     </indexterm>
 
     <para>
-      The storage requirements for each of the data types supported by
-      MySQL are listed here by category.
+      The storage requirements for each data type supported by MySQL are
+      listed here by category.
     </para>
 
     <indexterm>


Thread
svn commit - mysqldoc@docsrva: r23046 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-5.5 refman-5.6 refman-6.0paul.dubois7 Oct