List:Commits« Previous MessageNext Message »
From:paul Date:January 4 2006 4:14am
Subject:svn commit - mysqldoc@docsrva: r663 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-common
View as plain text  
Author: paul
Date: 2006-01-04 05:14:02 +0100 (Wed, 04 Jan 2006)
New Revision: 663

Log:
 r5807@frost:  paul | 2006-01-03 21:59:42 -0600
 General revisions.


Modified:
   trunk/
   trunk/refman-4.1/data-types.xml
   trunk/refman-4.1/introduction.xml
   trunk/refman-5.0/data-types.xml
   trunk/refman-5.0/introduction.xml
   trunk/refman-5.1/data-types.xml
   trunk/refman-5.1/introduction.xml
   trunk/refman-common/credits.xml


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

Modified: trunk/refman-4.1/data-types.xml
===================================================================
--- trunk/refman-4.1/data-types.xml	2006-01-04 04:13:33 UTC (rev 662)
+++ trunk/refman-4.1/data-types.xml	2006-01-04 04:14:02 UTC (rev 663)
@@ -338,7 +338,7 @@
           </para>
 
           <para>
-            A medium-size integer. The signed range is
+            A medium-sized integer. The signed range is
             <literal>-8388608</literal> to <literal>8388607</literal>.
             The unsigned range is <literal>0</literal> to
             <literal>16777215</literal>.

Modified: trunk/refman-4.1/introduction.xml
===================================================================
--- trunk/refman-4.1/introduction.xml	2006-01-04 04:13:33 UTC (rev 662)
+++ trunk/refman-4.1/introduction.xml	2006-01-04 04:14:02 UTC (rev 663)
@@ -1103,6 +1103,8 @@
   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../refman-common/information-sources.xml"/>
   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../refman-common/bug-reports.xml"/>
 
+  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../refman-common/bug-reports.xml"/>
+
   <section id="compatibility">
 
     <title>&title-compatibility;</title>
@@ -1136,7 +1138,7 @@
       standards. MySQL Server has many extensions to the SQL standard,
       and here you can find out what they are and how to use them. You
       can also find information about functionality missing from MySQL
-      Server, and how to work around some differences.
+      Server, and how to work around some of the differences.
     </para>
 
     <para>
@@ -1145,8 +1147,8 @@
       standard released in 1992, <quote>SQL:1999</quote> refers to the
       standard released in 1999, and <quote>SQL:2003</quote> refers to
       the current version of the standard. We use the phrase <quote>the
-      SQL standard</quote> to mean the current version of the SQL
-      Standard at any time.
+      SQL standard</quote> or <quote>standard SQL</quote> to mean the
+      current version of the SQL Standard at any time.
     </para>
 
     <para>
@@ -1163,8 +1165,8 @@
       speed or reliability. We are not afraid to add extensions to SQL
       or support for non-SQL features if this greatly increases the
       usability of MySQL Server for a large segment of our user base.
-      The <literal>HANDLER</literal> interface in MySQL Server 4.0 is an
-      example of this strategy. See <xref linkend="handler"/>.
+      The <literal>HANDLER</literal> interface is an example of this
+      strategy. See <xref linkend="handler"/>.
     </para>
 
     <para>
@@ -1174,9 +1176,9 @@
     </para>
 
     <para>
-      MySQL Server was originally designed to work with medium size
+      MySQL Server was originally designed to work with medium-sized
       databases (10-100 million rows, or about 100MB per table) on small
-      computer systems. Today MySQL Server handles terabyte-size
+      computer systems. Today MySQL Server handles terabyte-sized
       databases, but the code can also be compiled in a reduced version
       suitable for hand-held and embedded devices. The compact design of
       the MySQL server makes development in both directions possible
@@ -1205,8 +1207,8 @@
       <title>&title-standards;</title>
 
       <para>
-        We are aiming toward supporting the full ANSI/ISO SQL standard,
-        but without making concessions to speed and quality of the code.
+        Our aim is to support the full ANSI/ISO SQL standard, but
+        without making concessions to speed and quality of the code.
       </para>
 
       <para>
@@ -1222,28 +1224,31 @@
       <para>
         The MySQL server can operate in different SQL modes, and can
         apply these modes differentially for different clients. This
-        allows an application to tailor server operation to its own
-        requirements.
+        capability allows applications to tailor server operation to
+        their own requirements.
       </para>
 
       <para>
-        Modes define what SQL syntax MySQL should support and what kind
-        of validation checks it should perform on the data. This makes
-        it easier to use MySQL in a lot of different environments and to
-        use MySQL together with other database servers.
+        SQL modes control aspects of server operation such as what SQL
+        syntax MySQL should support and what kind of data validation
+        checks it should perform. This makes it easier to use MySQL in
+        different environments and to use MySQL together with other
+        database servers.
       </para>
 
       <para>
         You can set the default SQL mode by starting
         <command>mysqld</command> with the
-        <option>--sql-mode="modes"</option> option. Beginning with MySQL
-        4.1, you can also change the mode after startup time by setting
-        the <literal>sql_mode</literal> variable with a <literal>SET
-        [SESSION|GLOBAL] sql_mode='modes'</literal> statement.
+        <option>--sql-mode="<replaceable>mode_value</replaceable>"</option>
+        option. Beginning with MySQL 4.1, you can also change the mode
+        at runtime by setting the <literal>sql_mode</literal> system
+        variable with a <literal>SET [SESSION|GLOBAL]
+        sql_mode='<replaceable>mode_value</replaceable>'</literal>
+        statement.
       </para>
 
       <para>
-        For more information on setting the server mode, see
+        For more information on setting the SQL mode, see
         <xref linkend="server-sql-mode"/>.
       </para>
 
@@ -1321,10 +1326,10 @@
       </indexterm>
 
       <para>
-        The MySQL Server includes some extensions that you probably
-        won't find in other SQL DBMSs. Be warned that if you use them,
-        your code won't be portable to other SQL servers. In some cases,
-        you can write code that includes MySQL extensions, but is still
+        MySQL Server supports some extensions that you probably won't
+        find in other SQL DBMSs. Be warned that if you use them, your
+        code won't be portable to other SQL servers. In some cases, you
+        can write code that includes MySQL extensions, but is still
         portable, by using comments of the form <literal>/*! ...
         */</literal>. In this case, MySQL Server parses and execute the
         code within the comment as it would any other MySQL statement,

Modified: trunk/refman-5.0/data-types.xml
===================================================================
--- trunk/refman-5.0/data-types.xml	2006-01-04 04:13:33 UTC (rev 662)
+++ trunk/refman-5.0/data-types.xml	2006-01-04 04:14:02 UTC (rev 663)
@@ -354,7 +354,7 @@
           </para>
 
           <para>
-            A medium-size integer. The signed range is
+            A medium-sized integer. The signed range is
             <literal>-8388608</literal> to <literal>8388607</literal>.
             The unsigned range is <literal>0</literal> to
             <literal>16777215</literal>.

Modified: trunk/refman-5.0/introduction.xml
===================================================================
--- trunk/refman-5.0/introduction.xml	2006-01-04 04:13:33 UTC (rev 662)
+++ trunk/refman-5.0/introduction.xml	2006-01-04 04:14:02 UTC (rev 663)
@@ -743,7 +743,7 @@
       standards. MySQL Server has many extensions to the SQL standard,
       and here you can find out what they are and how to use them. You
       can also find information about functionality missing from MySQL
-      Server, and how to work around some differences.
+      Server, and how to work around some of the differences.
     </para>
 
     <para>
@@ -752,8 +752,8 @@
       standard released in 1992, <quote>SQL:1999</quote> refers to the
       standard released in 1999, and <quote>SQL:2003</quote> refers to
       the current version of the standard. We use the phrase <quote>the
-      SQL standard</quote> to mean the current version of the SQL
-      Standard at any time.
+      SQL standard</quote> or <quote>standard SQL</quote> to mean the
+      current version of the SQL Standard at any time.
     </para>
 
     <para>
@@ -770,8 +770,8 @@
       speed or reliability. We are not afraid to add extensions to SQL
       or support for non-SQL features if this greatly increases the
       usability of MySQL Server for a large segment of our user base.
-      The <literal>HANDLER</literal> interface in MySQL Server 4.0 is an
-      example of this strategy. See <xref linkend="handler"/>.
+      The <literal>HANDLER</literal> interface is an example of this
+      strategy. See <xref linkend="handler"/>.
     </para>
 
     <para>
@@ -781,9 +781,9 @@
     </para>
 
     <para>
-      MySQL Server was originally designed to work with medium size
+      MySQL Server was originally designed to work with medium-sized
       databases (10-100 million rows, or about 100MB per table) on small
-      computer systems. Today MySQL Server handles terabyte-size
+      computer systems. Today MySQL Server handles terabyte-sized
       databases, but the code can also be compiled in a reduced version
       suitable for hand-held and embedded devices. The compact design of
       the MySQL server makes development in both directions possible
@@ -812,8 +812,8 @@
       <title>&title-standards;</title>
 
       <para>
-        We are aiming toward supporting the full ANSI/ISO SQL standard,
-        but without making concessions to speed and quality of the code.
+        Our aim is to support the full ANSI/ISO SQL standard, but
+        without making concessions to speed and quality of the code.
       </para>
 
       <para>
@@ -829,28 +829,31 @@
       <para>
         The MySQL server can operate in different SQL modes, and can
         apply these modes differentially for different clients. This
-        allows an application to tailor server operation to its own
-        requirements.
+        capability allows applications to tailor server operation to
+        their own requirements.
       </para>
 
       <para>
-        Modes define what SQL syntax MySQL should support and what kind
-        of validation checks it should perform on the data. This makes
-        it easier to use MySQL in a lot of different environments and to
-        use MySQL together with other database servers.
+        SQL modes control aspects of server operation such as what SQL
+        syntax MySQL should support and what kind of data validation
+        checks it should perform. This makes it easier to use MySQL in
+        different environments and to use MySQL together with other
+        database servers.
       </para>
 
       <para>
         You can set the default SQL mode by starting
         <command>mysqld</command> with the
-        <option>--sql-mode="modes"</option> option. Beginning with MySQL
-        4.1, you can also change the mode after startup time by setting
-        the <literal>sql_mode</literal> variable with a <literal>SET
-        [SESSION|GLOBAL] sql_mode='modes'</literal> statement.
+        <option>--sql-mode="<replaceable>mode_value</replaceable>"</option>
+        option. Beginning with MySQL 4.1, you can also change the mode
+        at runtime by setting the <literal>sql_mode</literal> system
+        variable with a <literal>SET [SESSION|GLOBAL]
+        sql_mode='<replaceable>mode_value</replaceable>'</literal>
+        statement.
       </para>
 
       <para>
-        For more information on setting the server mode, see
+        For more information on setting the SQL mode, see
         <xref linkend="server-sql-mode"/>.
       </para>
 
@@ -928,10 +931,10 @@
       </indexterm>
 
       <para>
-        The MySQL Server includes some extensions that you probably
-        won't find in other SQL DBMSs. Be warned that if you use them,
-        your code won't be portable to other SQL servers. In some cases,
-        you can write code that includes MySQL extensions, but is still
+        MySQL Server supports some extensions that you probably won't
+        find in other SQL DBMSs. Be warned that if you use them, your
+        code won't be portable to other SQL servers. In some cases, you
+        can write code that includes MySQL extensions, but is still
         portable, by using comments of the form <literal>/*! ...
         */</literal>. In this case, MySQL Server parses and execute the
         code within the comment as it would any other MySQL statement,

Modified: trunk/refman-5.1/data-types.xml
===================================================================
--- trunk/refman-5.1/data-types.xml	2006-01-04 04:13:33 UTC (rev 662)
+++ trunk/refman-5.1/data-types.xml	2006-01-04 04:14:02 UTC (rev 663)
@@ -346,7 +346,7 @@
           </para>
 
           <para>
-            A medium-size integer. The signed range is
+            A medium-sized integer. The signed range is
             <literal>-8388608</literal> to <literal>8388607</literal>.
             The unsigned range is <literal>0</literal> to
             <literal>16777215</literal>.

Modified: trunk/refman-5.1/introduction.xml
===================================================================
--- trunk/refman-5.1/introduction.xml	2006-01-04 04:13:33 UTC (rev 662)
+++ trunk/refman-5.1/introduction.xml	2006-01-04 04:14:02 UTC (rev 663)
@@ -497,7 +497,7 @@
       standards. MySQL Server has many extensions to the SQL standard,
       and here you can find out what they are and how to use them. You
       can also find information about functionality missing from MySQL
-      Server, and how to work around some differences.
+      Server, and how to work around some of the differences.
     </para>
 
     <para>
@@ -506,8 +506,8 @@
       standard released in 1992, <quote>SQL:1999</quote> refers to the
       standard released in 1999, and <quote>SQL:2003</quote> refers to
       the current version of the standard. We use the phrase <quote>the
-      SQL standard</quote> to mean the current version of the SQL
-      Standard at any time.
+      SQL standard</quote> or <quote>standard SQL</quote> to mean the
+      current version of the SQL Standard at any time.
     </para>
 
     <para>
@@ -524,8 +524,8 @@
       speed or reliability. We are not afraid to add extensions to SQL
       or support for non-SQL features if this greatly increases the
       usability of MySQL Server for a large segment of our user base.
-      The <literal>HANDLER</literal> interface in MySQL Server 4.0 is an
-      example of this strategy. See <xref linkend="handler"/>.
+      The <literal>HANDLER</literal> interface is an example of this
+      strategy. See <xref linkend="handler"/>.
     </para>
 
     <para>
@@ -535,9 +535,9 @@
     </para>
 
     <para>
-      MySQL Server was originally designed to work with medium size
+      MySQL Server was originally designed to work with medium-sized
       databases (10-100 million rows, or about 100MB per table) on small
-      computer systems. Today MySQL Server handles terabyte-size
+      computer systems. Today MySQL Server handles terabyte-sized
       databases, but the code can also be compiled in a reduced version
       suitable for hand-held and embedded devices. The compact design of
       the MySQL server makes development in both directions possible
@@ -566,8 +566,8 @@
       <title>&title-standards;</title>
 
       <para>
-        We are aiming toward supporting the full ANSI/ISO SQL standard,
-        but without making concessions to speed and quality of the code.
+        Our aim is to support the full ANSI/ISO SQL standard, but
+        without making concessions to speed and quality of the code.
       </para>
 
       <para>
@@ -583,28 +583,31 @@
       <para>
         The MySQL server can operate in different SQL modes, and can
         apply these modes differentially for different clients. This
-        allows an application to tailor server operation to its own
-        requirements.
+        capability allows applications to tailor server operation to
+        their own requirements.
       </para>
 
       <para>
-        Modes define what SQL syntax MySQL should support and what kind
-        of validation checks it should perform on the data. This makes
-        it easier to use MySQL in a lot of different environments and to
-        use MySQL together with other database servers.
+        SQL modes control aspects of server operation such as what SQL
+        syntax MySQL should support and what kind of data validation
+        checks it should perform. This makes it easier to use MySQL in
+        different environments and to use MySQL together with other
+        database servers.
       </para>
 
       <para>
         You can set the default SQL mode by starting
         <command>mysqld</command> with the
-        <option>--sql-mode="modes"</option> option. Beginning with MySQL
-        4.1, you can also change the mode after startup time by setting
-        the <literal>sql_mode</literal> variable with a <literal>SET
-        [SESSION|GLOBAL] sql_mode='modes'</literal> statement.
+        <option>--sql-mode="<replaceable>mode_value</replaceable>"</option>
+        option. Beginning with MySQL 4.1, you can also change the mode
+        at runtime by setting the <literal>sql_mode</literal> system
+        variable with a <literal>SET [SESSION|GLOBAL]
+        sql_mode='<replaceable>mode_value</replaceable>'</literal>
+        statement.
       </para>
 
       <para>
-        For more information on setting the server mode, see
+        For more information on setting the SQL mode, see
         <xref linkend="server-sql-mode"/>.
       </para>
 
@@ -682,10 +685,10 @@
       </indexterm>
 
       <para>
-        The MySQL Server includes some extensions that you probably
-        won't find in other SQL DBMSs. Be warned that if you use them,
-        your code won't be portable to other SQL servers. In some cases,
-        you can write code that includes MySQL extensions, but is still
+        MySQL Server supports some extensions that you probably won't
+        find in other SQL DBMSs. Be warned that if you use them, your
+        code won't be portable to other SQL servers. In some cases, you
+        can write code that includes MySQL extensions, but is still
         portable, by using comments of the form <literal>/*! ...
         */</literal>. In this case, MySQL Server parses and execute the
         code within the comment as it would any other MySQL statement,

Modified: trunk/refman-common/credits.xml
===================================================================
--- trunk/refman-common/credits.xml	2006-01-04 04:13:33 UTC (rev 662)
+++ trunk/refman-common/credits.xml	2006-01-04 04:14:02 UTC (rev 663)
@@ -1784,9 +1784,8 @@
         </para>
 
         <para>
-          Not yet specified, but is flexible and can handle Linux and
-          maybe HP-UX. Tries to get user to use
-          <command>mysqlbug</command>.
+          Is flexible and can handle Linux and perhaps HP-UX. Tries to
+          get users to use <command>mysqlbug</command>.
         </para>
       </listitem>
 

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