List:Commits« Previous MessageNext Message »
From:paul Date:January 18 2006 7:31pm
Subject:svn commit - mysqldoc@docsrva: r904 - in trunk: . refman-4.1 refman-5.0 refman-5.1
View as plain text  
Author: paul
Date: 2006-01-18 20:31:50 +0100 (Wed, 18 Jan 2006)
New Revision: 904

Log:
 r2297@kite-hub:  paul | 2006-01-18 12:30:39 -0600
 General revisions.


Modified:
   trunk/
   trunk/refman-4.1/data-types.xml
   trunk/refman-4.1/problems.xml
   trunk/refman-5.0/data-types.xml
   trunk/refman-5.0/problems.xml
   trunk/refman-5.1/data-types.xml
   trunk/refman-5.1/problems.xml


Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6354
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2296
   + b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6354
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2297

Modified: trunk/refman-4.1/data-types.xml
===================================================================
--- trunk/refman-4.1/data-types.xml	2006-01-18 19:31:35 UTC (rev 903)
+++ trunk/refman-4.1/data-types.xml	2006-01-18 19:31:50 UTC (rev 904)
@@ -21,16 +21,16 @@
     chapter first gives an overview of these data types, and then
     provides a more detailed description of the properties of the types
     in each category, and a summary of the data type storage
-    requirements. The overview is intentionally brief. The more detailed
-    descriptions should be consulted for additional information about
-    particular data types, such as the allowable formats in which you
-    can specify values.
+    requirements. The initial overview is intentionally brief. The more
+    detailed descriptions later in the chapter should be consulted for
+    additional information about particular data types, such as the
+    allowable formats in which you can specify values.
   </para>
 
   <para>
-    MySQL versions 4.1 and up support extensions for handing spatial
-    data. Information about spatial types is provided in
-    <xref linkend="spatial-extensions"/>.
+    MySQL 4.1 and up also supports extensions for handing spatial data.
+    <xref linkend="spatial-extensions"/>, provides information about
+    these data types.
   </para>
 
   <indexterm>
@@ -43,13 +43,13 @@
   </indexterm>
 
   <indexterm>
-    <primary>columns</primary>
+    <primary>column</primary>
     <secondary>types</secondary>
   </indexterm>
 
   <indexterm>
     <primary>types</primary>
-    <secondary>columns</secondary>
+    <secondary>column</secondary>
   </indexterm>
 
   <para>
@@ -78,13 +78,13 @@
           <secondary>display</secondary>
         </indexterm>
 
-        <literal><replaceable>M</replaceable></literal>
+        <literal><replaceable>M</replaceable></literal> indicates the
+        maximum display width for integer types. For floating-point and
+        fixed-point types, <replaceable>M</replaceable> is the total
+        number of digits. For string types, <replaceable>M</replaceable>
+        is the maximum length. The maximum allowable value of
+        <replaceable>M</replaceable> depends on the data type.
       </para>
-
-      <para>
-        Indicates the maximum display width. The maximum legal display
-        width is 255.
-      </para>
     </listitem>
 
     <listitem>
@@ -97,13 +97,10 @@
           <primary>decimal point</primary>
         </indexterm>
 
-        <literal><replaceable>D</replaceable></literal>
-      </para>
-
-      <para>
-        Applies to floating-point and fixed-point types and indicates
-        the number of digits following the decimal point. The maximum
-        possible value is 30, but should be no greater than
+        <literal><replaceable>D</replaceable></literal> applies to
+        floating-point and fixed-point types and indicates the number of
+        digits following the decimal point. The maximum possible value
+        is 30, but should be no greater than
         <replaceable>M</replaceable>&minus;2.
       </para>
     </listitem>
@@ -120,8 +117,8 @@
         </indexterm>
 
         Square brackets (&lsquo;<literal>[</literal>&rsquo; and
-        &lsquo;<literal>]</literal>&rsquo;) indicate parts of type
-        specifiers that are optional.
+        &lsquo;<literal>]</literal>&rsquo;) indicate optional parts of
+        type definitions.
       </para>
     </listitem>
 
@@ -172,10 +169,10 @@
       </para>
 
       <para>
-        <emphasis role="bold">Warning</emphasis>: You should be aware
-        that when you use subtraction between integer values where one
-        is of type <literal>UNSIGNED</literal>, the result is unsigned.
-        See <xref linkend="cast-functions"/>.
+        <emphasis role="bold">Warning</emphasis>: When you use
+        subtraction between integer values where one is of type
+        <literal>UNSIGNED</literal>, the result is unsigned. See
+        <xref linkend="cast-functions"/>.
       </para>
 
       <itemizedlist>
@@ -272,10 +269,10 @@
           </para>
 
           <para>
-            These are synonyms for <literal>TINYINT(1)</literal>. The
-            <literal>BOOLEAN</literal> synonym was added in MySQL 4.1.0.
-            A value of zero is considered false. Non-zero values are
-            considered true.
+            These types are synonyms for <literal>TINYINT(1)</literal>.
+            The <literal>BOOLEAN</literal> synonym was added in MySQL
+            4.1.0. A value of zero is considered false. Non-zero values
+            are considered true.
           </para>
 
           <remark role="help-description-end"/>
@@ -400,7 +397,7 @@
           </para>
 
           <para>
-            This is a synonym for <literal>INT</literal>.
+            This type is a synonym for <literal>INT</literal>.
           </para>
 
           <remark role="help-description-end"/>
@@ -571,8 +568,8 @@
           </para>
 
           <para>
-            If <literal>UNSIGNED</literal> is specified, negative values
-            are disallowed.
+            <literal>UNSIGNED</literal>, if specified, disallows
+            negative values.
           </para>
 
           <para>
@@ -642,8 +639,8 @@
           </para>
 
           <para>
-            If <literal>UNSIGNED</literal> is specified, negative values
-            are disallowed.
+            <literal>UNSIGNED</literal>, if specified, disallows
+            negative values.
           </para>
 
           <remark role="help-description-end"/>
@@ -681,9 +678,9 @@
           </para>
 
           <para>
-            These are synonyms for <literal>DOUBLE</literal>. Exception:
-            If the <literal>REAL_AS_FLOAT</literal> SQL mode is
-            enabled,, <literal>REAL</literal> is a synonym for
+            These types are synonyms for <literal>DOUBLE</literal>.
+            Exception: If the <literal>REAL_AS_FLOAT</literal> SQL mode
+            is enabled, <literal>REAL</literal> is a synonym for
             <literal>FLOAT</literal> rather than
             <literal>DOUBLE</literal>.
           </para>
@@ -713,11 +710,10 @@
           <para>
             A floating-point number. <replaceable>p</replaceable>
             represents the precision in bits, but MySQL uses this value
-            only to determine whether to give the resulting column a
-            data type of <literal>FLOAT</literal> or
-            <literal>DOUBLE</literal>. If <replaceable>p</replaceable>
-            is from 0 to 24, the data type becomes
-            <literal>FLOAT</literal> with no
+            only to determine whether to use <literal>FLOAT</literal> or
+            <literal>DOUBLE</literal> for the resulting data type. If
+            <replaceable>p</replaceable> is from 0 to 24, the data type
+            becomes <literal>FLOAT</literal> with no
             <replaceable>M</replaceable> or <replaceable>D</replaceable>
             values. If <replaceable>p</replaceable> is from 25 to 53,
             the data type becomes <literal>DOUBLE</literal> with no
@@ -796,8 +792,8 @@
           </para>
 
           <para>
-            If <literal>UNSIGNED</literal> is specified, negative values
-            are disallowed.
+            <literal>UNSIGNED</literal>, if specified, disallows
+            negative values.
           </para>
 
           <para>
@@ -856,7 +852,7 @@
           </para>
 
           <para>
-            These are synonyms for <literal>DECIMAL</literal>. The
+            These types are synonyms for <literal>DECIMAL</literal>. The
             <literal>FIXED</literal> synonym was added in MySQL 4.1.0
             for compatibility with other servers.
           </para>
@@ -1373,7 +1369,7 @@
           </para>
 
           <para>
-            This is a synonym for <literal>CHAR(1)</literal>.
+            This type is a synonym for <literal>CHAR(1)</literal>.
           </para>
         </listitem>
 

Modified: trunk/refman-4.1/problems.xml
===================================================================
--- trunk/refman-4.1/problems.xml	2006-01-18 19:31:35 UTC (rev 903)
+++ trunk/refman-4.1/problems.xml	2006-01-18 19:31:50 UTC (rev 904)
@@ -3172,12 +3172,19 @@
       <para>
         The default location for the Unix socket file that the server
         uses for communication with local clients is
-        <filename>/tmp/mysql.sock</filename>. This might cause problems,
-        because on some versions of Unix, anyone can delete files in the
-        <filename>/tmp</filename> directory.
+        <filename>/tmp/mysql.sock</filename>. (For some distribution
+        formats, the directory might be different, such as
+        <filename>/var/lib/mysql</filename> for RPMs.)
       </para>
 
       <para>
+        On some versions of Unix, anyone can delete files in the
+        <filename>/tmp</filename> directory or other similar directories
+        used for temporary files. If the socket file is located in such
+        a directory on your system, this might cause problems.
+      </para>
+
+      <para>
         On most versions of Unix, you can protect your
         <filename>/tmp</filename> directory so that files can be deleted
         only by their owners or the superuser (<literal>root</literal>).
@@ -5097,11 +5104,11 @@
 
         <listitem>
           <para>
-            Due to the way table format (<filename>.frm</filename>) files are stored, you cannot
-            use character 255 (<literal>CHAR(255)</literal>) in table
-            names, column names, or enumerations. This is scheduled to
-            be fixed in version 5.1 when we implement new table
-            definition format files.
+            Due to the way table format (<filename>.frm</filename>)
+            files are stored, you cannot use character 255
+            (<literal>CHAR(255)</literal>) in table names, column names,
+            or enumerations. This is scheduled to be fixed in version
+            5.1 when we implement new table definition format files.
           </para>
         </listitem>
 

Modified: trunk/refman-5.0/data-types.xml
===================================================================
--- trunk/refman-5.0/data-types.xml	2006-01-18 19:31:35 UTC (rev 903)
+++ trunk/refman-5.0/data-types.xml	2006-01-18 19:31:50 UTC (rev 904)
@@ -21,16 +21,16 @@
     chapter first gives an overview of these data types, and then
     provides a more detailed description of the properties of the types
     in each category, and a summary of the data type storage
-    requirements. The overview is intentionally brief. The more detailed
-    descriptions should be consulted for additional information about
-    particular data types, such as the allowable formats in which you
-    can specify values.
+    requirements. The initial overview is intentionally brief. The more
+    detailed descriptions later in the chapter should be consulted for
+    additional information about particular data types, such as the
+    allowable formats in which you can specify values.
   </para>
 
   <para>
-    MySQL supports extensions for handing spatial data. Information
-    about spatial types is provided in
-    <xref linkend="spatial-extensions"/>.
+    MySQL also supports extensions for handing spatial data.
+    <xref linkend="spatial-extensions"/>, provides information about
+    these data types.
   </para>
 
   <indexterm>
@@ -43,13 +43,13 @@
   </indexterm>
 
   <indexterm>
-    <primary>columns</primary>
+    <primary>column</primary>
     <secondary>types</secondary>
   </indexterm>
 
   <indexterm>
     <primary>types</primary>
-    <secondary>columns</secondary>
+    <secondary>column</secondary>
   </indexterm>
 
   <para>
@@ -58,10 +58,6 @@
 
   <itemizedlist>
 
-    <remark role="todo">
-      Convert to an informaltable?
-    </remark>
-
     <listitem>
       <para>
         <indexterm>
@@ -82,13 +78,13 @@
           <secondary>display</secondary>
         </indexterm>
 
-        <literal><replaceable>M</replaceable></literal>
+        <literal><replaceable>M</replaceable></literal> indicates the
+        maximum display width for integer types. For floating-point and
+        fixed-point types, <replaceable>M</replaceable> is the total
+        number of digits. For string types, <replaceable>M</replaceable>
+        is the maximum length. The maximum allowable value of
+        <replaceable>M</replaceable> depends on the data type.
       </para>
-
-      <para>
-        Indicates the maximum display width. The maximum legal display
-        width is 255.
-      </para>
     </listitem>
 
     <listitem>
@@ -101,13 +97,10 @@
           <primary>decimal point</primary>
         </indexterm>
 
-        <literal><replaceable>D</replaceable></literal>
-      </para>
-
-      <para>
-        Applies to floating-point and fixed-point types and indicates
-        the number of digits following the decimal point. The maximum
-        possible value is 30, but should be no greater than
+        <literal><replaceable>D</replaceable></literal> applies to
+        floating-point and fixed-point types and indicates the number of
+        digits following the decimal point. The maximum possible value
+        is 30, but should be no greater than
         <replaceable>M</replaceable>&minus;2.
       </para>
     </listitem>
@@ -124,8 +117,8 @@
         </indexterm>
 
         Square brackets (&lsquo;<literal>[</literal>&rsquo; and
-        &lsquo;<literal>]</literal>&rsquo;) indicate parts of type
-        specifiers that are optional.
+        &lsquo;<literal>]</literal>&rsquo;) indicate optional parts of
+        type definitions.
       </para>
     </listitem>
 
@@ -176,10 +169,10 @@
       </para>
 
       <para>
-        <emphasis role="bold">Warning:</emphasis> You should be aware
-        that when you use subtraction between integer values where one
-        is of type <literal>UNSIGNED</literal>, the result is unsigned.
-        See <xref linkend="cast-functions"/>.
+        <emphasis role="bold">Warning</emphasis>: When you use
+        subtraction between integer values where one is of type
+        <literal>UNSIGNED</literal>, the result is unsigned. See
+        <xref linkend="cast-functions"/>.
       </para>
 
       <itemizedlist>
@@ -284,8 +277,8 @@
           </para>
 
           <para>
-            These are synonyms for <literal>TINYINT(1)</literal>. A
-            value of zero is considered false. Non-zero values are
+            These types are synonyms for <literal>TINYINT(1)</literal>.
+            A value of zero is considered false. Non-zero values are
             considered true.
           </para>
 
@@ -416,7 +409,7 @@
           </para>
 
           <para>
-            This is a synonym for <literal>INT</literal>.
+            This type is a synonym for <literal>INT</literal>.
           </para>
 
           <remark role="help-description-end"/>
@@ -587,8 +580,8 @@
           </para>
 
           <para>
-            If <literal>UNSIGNED</literal> is specified, negative values
-            are disallowed.
+            <literal>UNSIGNED</literal>, if specified, disallows
+            negative values.
           </para>
 
           <para>
@@ -658,8 +651,8 @@
           </para>
 
           <para>
-            If <literal>UNSIGNED</literal> is specified, negative values
-            are disallowed.
+            <literal>UNSIGNED</literal>, if specified, disallows
+            negative values.
           </para>
 
           <remark role="help-description-end"/>
@@ -697,9 +690,9 @@
           </para>
 
           <para>
-            These are synonyms for <literal>DOUBLE</literal>. Exception:
-            If the <literal>REAL_AS_FLOAT</literal> SQL mode is
-            enabled,, <literal>REAL</literal> is a synonym for
+            These types are synonyms for <literal>DOUBLE</literal>.
+            Exception: If the <literal>REAL_AS_FLOAT</literal> SQL mode
+            is enabled, <literal>REAL</literal> is a synonym for
             <literal>FLOAT</literal> rather than
             <literal>DOUBLE</literal>.
           </para>
@@ -729,11 +722,10 @@
           <para>
             A floating-point number. <replaceable>p</replaceable>
             represents the precision in bits, but MySQL uses this value
-            only to determine whether to give the resulting column a
-            data type of <literal>FLOAT</literal> or
-            <literal>DOUBLE</literal>. If <replaceable>p</replaceable>
-            is from 0 to 24, the data type becomes
-            <literal>FLOAT</literal> with no
+            only to determine whether to use <literal>FLOAT</literal> or
+            <literal>DOUBLE</literal> for the resulting data type. If
+            <replaceable>p</replaceable> is from 0 to 24, the data type
+            becomes <literal>FLOAT</literal> with no
             <replaceable>M</replaceable> or <replaceable>D</replaceable>
             values. If <replaceable>p</replaceable> is from 25 to 53,
             the data type becomes <literal>DOUBLE</literal> with no
@@ -806,8 +798,8 @@
           </para>
 
           <para>
-            If <literal>UNSIGNED</literal> is specified, negative values
-            are disallowed.
+            <literal>UNSIGNED</literal>, if specified, disallows
+            negative values.
           </para>
 
           <para>
@@ -896,9 +888,9 @@
           </para>
 
           <para>
-            These are synonyms for <literal>DECIMAL</literal>. The
+            These types are synonyms for <literal>DECIMAL</literal>. The
             <literal>FIXED</literal> synonym is available for
-            compatibility with other servers.
+            compatibility with other database systems.
           </para>
 
           <remark role="help-description-end"/>
@@ -1389,7 +1381,7 @@
           </para>
 
           <para>
-            This is a synonym for <literal>CHAR(1)</literal>.
+            This type is a synonym for <literal>CHAR(1)</literal>.
           </para>
         </listitem>
 

Modified: trunk/refman-5.0/problems.xml
===================================================================
--- trunk/refman-5.0/problems.xml	2006-01-18 19:31:35 UTC (rev 903)
+++ trunk/refman-5.0/problems.xml	2006-01-18 19:31:50 UTC (rev 904)
@@ -3139,12 +3139,19 @@
       <para>
         The default location for the Unix socket file that the server
         uses for communication with local clients is
-        <filename>/tmp/mysql.sock</filename>. This might cause problems,
-        because on some versions of Unix, anyone can delete files in the
-        <filename>/tmp</filename> directory.
+        <filename>/tmp/mysql.sock</filename>. (For some distribution
+        formats, the directory might be different, such as
+        <filename>/var/lib/mysql</filename> for RPMs.)
       </para>
 
       <para>
+        On some versions of Unix, anyone can delete files in the
+        <filename>/tmp</filename> directory or other similar directories
+        used for temporary files. If the socket file is located in such
+        a directory on your system, this might cause problems.
+      </para>
+
+      <para>
         On most versions of Unix, you can protect your
         <filename>/tmp</filename> directory so that files can be deleted
         only by their owners or the superuser (<literal>root</literal>).
@@ -4898,11 +4905,11 @@
 
         <listitem>
           <para>
-            Due to the way table format (<filename>.frm</filename>) files are stored, you cannot
-            use character 255 (<literal>CHAR(255)</literal>) in table
-            names, column names, or enumerations. This is scheduled to
-            be fixed in version 5.1 when we implement new table
-            definition format files.
+            Due to the way table format (<filename>.frm</filename>)
+            files are stored, you cannot use character 255
+            (<literal>CHAR(255)</literal>) in table names, column names,
+            or enumerations. This is scheduled to be fixed in version
+            5.1 when we implement new table definition format files.
           </para>
         </listitem>
 

Modified: trunk/refman-5.1/data-types.xml
===================================================================
--- trunk/refman-5.1/data-types.xml	2006-01-18 19:31:35 UTC (rev 903)
+++ trunk/refman-5.1/data-types.xml	2006-01-18 19:31:50 UTC (rev 904)
@@ -21,16 +21,16 @@
     chapter first gives an overview of these data types, and then
     provides a more detailed description of the properties of the types
     in each category, and a summary of the data type storage
-    requirements. The initial overview is intentionally brief. The more detailed
-    descriptions later in the chapter should be consulted for additional information about
-    particular data types, such as the allowable formats in which you
-    can specify values.
+    requirements. The initial overview is intentionally brief. The more
+    detailed descriptions later in the chapter should be consulted for
+    additional information about particular data types, such as the
+    allowable formats in which you can specify values.
   </para>
 
   <para>
-    MySQL supports extensions for handing spatial data. Information
-    about spatial types is provided in
-    <xref linkend="spatial-extensions"/>.
+    MySQL also supports extensions for handing spatial data.
+    <xref linkend="spatial-extensions"/>, provides information about
+    these data types.
   </para>
 
   <indexterm>
@@ -43,13 +43,13 @@
   </indexterm>
 
   <indexterm>
-    <primary>columns</primary>
+    <primary>column</primary>
     <secondary>types</secondary>
   </indexterm>
 
   <indexterm>
     <primary>types</primary>
-    <secondary>columns</secondary>
+    <secondary>column</secondary>
   </indexterm>
 
   <para>
@@ -58,10 +58,6 @@
 
   <itemizedlist>
 
-    <remark role="todo">
-      Convert to an informaltable?
-    </remark>
-
     <listitem>
       <para>
         <indexterm>
@@ -82,13 +78,13 @@
           <secondary>display</secondary>
         </indexterm>
 
-        <literal><replaceable>M</replaceable></literal>
+        <literal><replaceable>M</replaceable></literal> indicates the
+        maximum display width for integer types. For floating-point and
+        fixed-point types, <replaceable>M</replaceable> is the total
+        number of digits. For string types, <replaceable>M</replaceable>
+        is the maximum length. The maximum allowable value of
+        <replaceable>M</replaceable> depends on the data type.
       </para>
-
-      <para>
-        Indicates the maximum display width. The maximum legal display
-        width is 255.
-      </para>
     </listitem>
 
     <listitem>
@@ -101,13 +97,10 @@
           <primary>decimal point</primary>
         </indexterm>
 
-        <literal><replaceable>D</replaceable></literal>
-      </para>
-
-      <para>
-        Applies to floating-point and fixed-point types and indicates
-        the number of digits following the decimal point. The maximum
-        possible value is 30, but should be no greater than
+        <literal><replaceable>D</replaceable></literal> applies to
+        floating-point and fixed-point types and indicates the number of
+        digits following the decimal point. The maximum possible value
+        is 30, but should be no greater than
         <replaceable>M</replaceable>&minus;2.
       </para>
     </listitem>
@@ -124,8 +117,8 @@
         </indexterm>
 
         Square brackets (&lsquo;<literal>[</literal>&rsquo; and
-        &lsquo;<literal>]</literal>&rsquo;) indicate parts of type
-        specifiers that are optional.
+        &lsquo;<literal>]</literal>&rsquo;) indicate optional parts of
+        type definitions.
       </para>
     </listitem>
 
@@ -176,10 +169,10 @@
       </para>
 
       <para>
-        <emphasis role="bold">Warning:</emphasis> You should be aware
-        that when you use subtraction between integer values where one
-        is of type <literal>UNSIGNED</literal>, the result is unsigned.
-        See <xref linkend="cast-functions"/>.
+        <emphasis role="bold">Warning</emphasis>: When you use
+        subtraction between integer values where one is of type
+        <literal>UNSIGNED</literal>, the result is unsigned. See
+        <xref linkend="cast-functions"/>.
       </para>
 
       <itemizedlist>
@@ -276,8 +269,8 @@
           </para>
 
           <para>
-            These are synonyms for <literal>TINYINT(1)</literal>. A
-            value of zero is considered false. Non-zero values are
+            These types are synonyms for <literal>TINYINT(1)</literal>.
+            A value of zero is considered false. Non-zero values are
             considered true.
           </para>
 
@@ -408,7 +401,7 @@
           </para>
 
           <para>
-            This is a synonym for <literal>INT</literal>.
+            This type is a synonym for <literal>INT</literal>.
           </para>
 
           <remark role="help-description-end"/>
@@ -579,8 +572,8 @@
           </para>
 
           <para>
-            If <literal>UNSIGNED</literal> is specified, negative values
-            are disallowed.
+            <literal>UNSIGNED</literal>, if specified, disallows
+            negative values.
           </para>
 
           <para>
@@ -650,8 +643,8 @@
           </para>
 
           <para>
-            If <literal>UNSIGNED</literal> is specified, negative values
-            are disallowed.
+            <literal>UNSIGNED</literal>, if specified, disallows
+            negative values.
           </para>
 
           <remark role="help-description-end"/>
@@ -689,9 +682,9 @@
           </para>
 
           <para>
-            These are synonyms for <literal>DOUBLE</literal>. Exception:
-            If the <literal>REAL_AS_FLOAT</literal> SQL mode is
-            enabled,, <literal>REAL</literal> is a synonym for
+            These types are synonyms for <literal>DOUBLE</literal>.
+            Exception: If the <literal>REAL_AS_FLOAT</literal> SQL mode
+            is enabled, <literal>REAL</literal> is a synonym for
             <literal>FLOAT</literal> rather than
             <literal>DOUBLE</literal>.
           </para>
@@ -721,11 +714,10 @@
           <para>
             A floating-point number. <replaceable>p</replaceable>
             represents the precision in bits, but MySQL uses this value
-            only to determine whether to give the resulting column a
-            data type of <literal>FLOAT</literal> or
-            <literal>DOUBLE</literal>. If <replaceable>p</replaceable>
-            is from 0 to 24, the data type becomes
-            <literal>FLOAT</literal> with no
+            only to determine whether to use <literal>FLOAT</literal> or
+            <literal>DOUBLE</literal> for the resulting data type. If
+            <replaceable>p</replaceable> is from 0 to 24, the data type
+            becomes <literal>FLOAT</literal> with no
             <replaceable>M</replaceable> or <replaceable>D</replaceable>
             values. If <replaceable>p</replaceable> is from 25 to 53,
             the data type becomes <literal>DOUBLE</literal> with no
@@ -793,8 +785,8 @@
           </para>
 
           <para>
-            If <literal>UNSIGNED</literal> is specified, negative values
-            are disallowed.
+            <literal>UNSIGNED</literal>, if specified, disallows
+            negative values.
           </para>
 
           <para>
@@ -852,9 +844,9 @@
           </para>
 
           <para>
-            These are synonyms for <literal>DECIMAL</literal>. The
+            These types are synonyms for <literal>DECIMAL</literal>. The
             <literal>FIXED</literal> synonym is available for
-            compatibility with other servers.
+            compatibility with other database systems.
           </para>
 
           <remark role="help-description-end"/>
@@ -1333,7 +1325,7 @@
           </para>
 
           <para>
-            This is a synonym for <literal>CHAR(1)</literal>.
+            This type is a synonym for <literal>CHAR(1)</literal>.
           </para>
         </listitem>
 

Modified: trunk/refman-5.1/problems.xml
===================================================================
--- trunk/refman-5.1/problems.xml	2006-01-18 19:31:35 UTC (rev 903)
+++ trunk/refman-5.1/problems.xml	2006-01-18 19:31:50 UTC (rev 904)
@@ -3139,12 +3139,19 @@
       <para>
         The default location for the Unix socket file that the server
         uses for communication with local clients is
-        <filename>/tmp/mysql.sock</filename>. This might cause problems,
-        because on some versions of Unix, anyone can delete files in the
-        <filename>/tmp</filename> directory.
+        <filename>/tmp/mysql.sock</filename>. (For some distribution
+        formats, the directory might be different, such as
+        <filename>/var/lib/mysql</filename> for RPMs.)
       </para>
 
       <para>
+        On some versions of Unix, anyone can delete files in the
+        <filename>/tmp</filename> directory or other similar directories
+        used for temporary files. If the socket file is located in such
+        a directory on your system, this might cause problems.
+      </para>
+
+      <para>
         On most versions of Unix, you can protect your
         <filename>/tmp</filename> directory so that files can be deleted
         only by their owners or the superuser (<literal>root</literal>).
@@ -4879,11 +4886,11 @@
 
         <listitem>
           <para>
-            Due to the way table format (<filename>.frm</filename>) files are stored, you cannot
-            use character 255 (<literal>CHAR(255)</literal>) in table
-            names, column names, or enumerations. This is scheduled to
-            be fixed in version 5.1 when we implement new table
-            definition format files.
+            Due to the way table format (<filename>.frm</filename>)
+            files are stored, you cannot use character 255
+            (<literal>CHAR(255)</literal>) in table names, column names,
+            or enumerations. This is scheduled to be fixed in version
+            5.1 when we implement new table definition format files.
           </para>
         </listitem>
 

Thread
svn commit - mysqldoc@docsrva: r904 - in trunk: . refman-4.1 refman-5.0 refman-5.1paul18 Jan