MySQL Lists are EOL. Please join:

List:Commits« Previous MessageNext Message »
From:paul.dubois Date:July 28 2010 7:27pm
Subject:svn commit - mysqldoc@docsrva: r21950 - in trunk: . dynamic-docs/changelog innodb-plugin-1.0 innodb-plugin-1.1 mysql-monitor-common mysqltest-1.0 mysq...
View as plain text  
Author: paul
Date: 2010-07-28 21:27:14 +0200 (Wed, 28 Jul 2010)
New Revision: 21950

Log:
 r61700@frost:  paul | 2010-07-28 13:42:03 -0500
 Oracle style guidelines: alphabetical -> alphabetic, numerical -> numeric


Modified:
   trunk/dynamic-docs/changelog/connector-j.xml
   trunk/dynamic-docs/changelog/monitor.xml
   trunk/dynamic-docs/changelog/mysqld.xml
   trunk/dynamic-docs/changelog/workbench.xml
   trunk/innodb-plugin-1.0/innodb-file-format.xml
   trunk/innodb-plugin-1.1/innodb-file-format.xml
   trunk/mysql-monitor-common/dashboard-configure-core.xml
   trunk/mysqltest-1.0/preface.xml
   trunk/mysqltest-2.0/preface.xml
   trunk/mysqltest-2.0/programs.xml
   trunk/ndbapi/ndb-classes.xml
   trunk/refman-4.1/data-types.xml
   trunk/refman-4.1/news-3.23.xml
   trunk/refman-4.1/news-4.0.xml
   trunk/refman-4.1/optimization.xml
   trunk/refman-4.1/tutorial.xml
   trunk/refman-5.0/data-types.xml
   trunk/refman-5.0/information-schema.xml
   trunk/refman-5.0/optimization.xml
   trunk/refman-5.0/tutorial.xml
   trunk/refman-5.1/data-types.xml
   trunk/refman-5.1/functions-core.xml
   trunk/refman-5.1/information-schema.xml
   trunk/refman-5.1/optimization.xml
   trunk/refman-5.1/tutorial.xml
   trunk/refman-5.5/data-types.xml
   trunk/refman-5.5/functions-core.xml
   trunk/refman-5.5/information-schema.xml
   trunk/refman-5.5/optimization.xml
   trunk/refman-5.5/tutorial.xml
   trunk/refman-6.0/data-types.xml
   trunk/refman-6.0/functions-core.xml
   trunk/refman-6.0/information-schema.xml
   trunk/refman-6.0/optimization.xml
   trunk/refman-6.0/tutorial.xml
   trunk/refman-common/connector-j.xml
   trunk/refman-common/connector-net-programming.xml
   trunk/refman-common/connector-net-ref.xml
   trunk/refman-common/connector-odbc.xml
   trunk/refman-common/news-innodb.xml
   trunk/sample-data/sakila/sakila.xml
   trunk/workbench/table-editor.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:40851
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:61687
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:40851
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:61700
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/dynamic-docs/changelog/connector-j.xml
===================================================================
--- trunk/dynamic-docs/changelog/connector-j.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/dynamic-docs/changelog/connector-j.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 792 bytes

@@ -5121,7 +5121,7 @@
         Added experimental configuration property
         <literal>dontUnpackBinaryResults</literal>, which delays
         unpacking binary result set values until they're asked for, and
-        only creates object instances for nonnumerical values (it is set
+        only creates object instances for nonnumeric values (it is set
         to <literal>false</literal> by default). For some usecase/jvm
         combinations, this is friendlier on the garbage collector.
       </para>


Modified: trunk/dynamic-docs/changelog/monitor.xml
===================================================================
--- trunk/dynamic-docs/changelog/monitor.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/dynamic-docs/changelog/monitor.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 590 bytes

@@ -4183,7 +4183,7 @@
       <para>
         The Notifications list in the Schedules or Edit Schedules
         pop-ups listed the Notification Groups targets in the order in
-        which they were created, not alphabetical order.
+        which they were created, not alphabetic order.
       </para>
 
     </message>


Modified: trunk/dynamic-docs/changelog/mysqld.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/dynamic-docs/changelog/mysqld.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 789 bytes

@@ -1576,8 +1576,8 @@
         Performing a full text search on a table could cause a crash on
         a 64-bit platforms with certain characteristics. Searches that
         were known to cause a crash with certain datasets included
-        numerical values and strings where the match string included
-        data enclosed in single or double quotation marks.
+        numeric values and strings where the match string included data
+        enclosed in single or double quotation marks.
       </para>
 
     </message>


Modified: trunk/dynamic-docs/changelog/workbench.xml
===================================================================
--- trunk/dynamic-docs/changelog/workbench.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/dynamic-docs/changelog/workbench.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 3, Lines Added: 4, Lines Deleted: 4; 1175 bytes

@@ -10000,7 +10000,7 @@
 
       <para>
         In the Physical Schemata section of the MySQL Model tab, the
-        tables were not displayed in alphabetical order.
+        tables were not displayed in alphabetic order.
       </para>
 
     </message>

@@ -10266,8 +10266,8 @@
 
       <para>
         Client-side sorting always sorted on an alpha basis, regardless
-        of data type. This meant numerical values were not sorted into
-        the order expected.
+        of data type. This meant numeric values were not sorted into the
+        order expected.
       </para>
 
     </message>

@@ -12891,7 +12891,7 @@
 
       <para>
         &workbench; has been changed so that layers and tables listed in
-        the Layers palette are sorted in alphabetical order, making it
+        the Layers palette are sorted in alphabetic order, making it
         easier to find the required object.
       </para>
 


Modified: trunk/innodb-plugin-1.0/innodb-file-format.xml
===================================================================
--- trunk/innodb-plugin-1.0/innodb-file-format.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/innodb-plugin-1.0/innodb-file-format.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 616 bytes

@@ -70,7 +70,7 @@
       <quote>off-page</quote> require the use of the &q.barracuda; file
       format or newer. Future versions of &innodb; may introduce a
       series of file formats, identified with the names of animals, in
-      ascending alphabetical order.
+      ascending alphabetic order.
     </para>
 
     <para>


Modified: trunk/innodb-plugin-1.1/innodb-file-format.xml
===================================================================
--- trunk/innodb-plugin-1.1/innodb-file-format.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/innodb-plugin-1.1/innodb-file-format.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 662 bytes

@@ -47,7 +47,7 @@
     &q.barracuda; file format or newer. Future versions of &innodb; may
     introduce a series of file formats,
     <link linkend="innodb-file-format-future">identified with the names
-    of animals</link>, in ascending alphabetical order.
+    of animals</link>, in ascending alphabetic order.
   </para>
 
   <section id="innodb-file-format-enabling">


Modified: trunk/mysql-monitor-common/dashboard-configure-core.xml
===================================================================
--- trunk/mysql-monitor-common/dashboard-configure-core.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/mysql-monitor-common/dashboard-configure-core.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 5; 963 bytes

@@ -1078,11 +1078,10 @@
     </figure>
 
     <para>
-      The various categories of logs are shown in alphabetical order.
-      The most recent changes to each log are shown in the
-      <guilabel>Last Modified</guilabel> column. The number of entries
-      in any specific log is shown under the
-      <guilabel>Entries</guilabel> column.
+      The various categories of logs are shown in alphabetic order. The
+      most recent changes to each log are shown in the <guilabel>Last
+      Modified</guilabel> column. The number of entries in any specific
+      log is shown under the <guilabel>Entries</guilabel> column.
     </para>
 
     <para>


Modified: trunk/mysqltest-1.0/preface.xml
===================================================================
--- trunk/mysqltest-1.0/preface.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/mysqltest-1.0/preface.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 515 bytes

@@ -26,7 +26,7 @@
 
   <para>
     Much of the content of this manual is based on material originally
-    written by (in alphabetical order) Omer BarNir, Kent Boortz, and
+    written by (in alphabetic order) Omer BarNir, Kent Boortz, and
     Matthias Leich.
   </para>
 


Modified: trunk/mysqltest-2.0/preface.xml
===================================================================
--- trunk/mysqltest-2.0/preface.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/mysqltest-2.0/preface.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 578 bytes

@@ -26,7 +26,7 @@
 
   <para>
     Much of the content of this manual is based on material originally
-    written by (in alphabetical order) Omer BarNir, Kent Boortz, and
+    written by (in alphabetic order) Omer BarNir, Kent Boortz, and
     Matthias Leich. Updates and adaptions to version 2 was done by Bjorn
     Munch.
   </para>


Modified: trunk/mysqltest-2.0/programs.xml
===================================================================
--- trunk/mysqltest-2.0/programs.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/mysqltest-2.0/programs.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 4; 958 bytes

@@ -2907,10 +2907,10 @@
           <para>
             Do not reorder tests to reduce number of restarts, but run
             them in exactly the order given. If a whole suite is to be
-            run, the tests are run in alphabetical order, though
-            similiar combinations will be grouped together. If more than
-            one suite is listed, the tests are run one suite at a time,
-            in the order listed.
+            run, the tests are run in alphabetic order, though similiar
+            combinations will be grouped together. If more than one
+            suite is listed, the tests are run one suite at a time, in
+            the order listed.
           </para>
         </listitem>
 


Modified: trunk/ndbapi/ndb-classes.xml
===================================================================
--- trunk/ndbapi/ndb-classes.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/ndbapi/ndb-classes.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 491 bytes

@@ -64,7 +64,7 @@
 
   <para>
     Class, interface, and structure descriptions are provided in
-    alphabetical order. For a hierarchical listing, see
+    alphabetic order. For a hierarchical listing, see
     <xref linkend="ndb-hierarchy"/>.
   </para>
 


Modified: trunk/refman-4.1/data-types.xml
===================================================================
--- trunk/refman-4.1/data-types.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-4.1/data-types.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 2, Lines Added: 4, Lines Deleted: 4; 1361 bytes

@@ -5367,8 +5367,8 @@
             present in the list of permitted values), the empty string
             is inserted instead as a special error value. This string
             can be distinguished from a <quote>normal</quote> empty
-            string by the fact that this string has the numerical value
-            0. More about this later.
+            string by the fact that this string has the numeric value 0.
+            More about this later.
           </para>
 
           <para>

@@ -5571,8 +5571,8 @@
         <literal>NULL</literal> values sort before all other enumeration
         values. If you expect sorting to be done alphabetically, you
         should specify the <literal role="type">ENUM</literal> list in
-        alphabetical order. You can also use <literal>GROUP BY CAST(col
-        AS CHAR)</literal> or <literal>GROUP BY CONCAT(col)</literal> to
+        alphabetic order. You can also use <literal>GROUP BY CAST(col AS
+        CHAR)</literal> or <literal>GROUP BY CONCAT(col)</literal> to
         make sure that the column is sorted lexically rather than by
         index number.
       </para>


Modified: trunk/refman-4.1/news-3.23.xml
===================================================================
--- trunk/refman-4.1/news-3.23.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-4.1/news-3.23.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 463 bytes

@@ -8903,7 +8903,7 @@
       <listitem>
         <para>
           Do not allow <literal>AUTO_INCREMENT</literal> for other than
-          numerical columns.
+          numeric columns.
         </para>
       </listitem>
 


Modified: trunk/refman-4.1/news-4.0.xml
===================================================================
--- trunk/refman-4.1/news-4.0.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-4.1/news-4.0.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 532 bytes

@@ -8010,7 +8010,7 @@
       <listitem>
         <para>
           <literal role="stmt" condition="flush">FLUSH LOGS</literal>
-          removed numerical extension for all future update logs.
+          removed numeric extension for all future update logs.
         </para>
       </listitem>
 


Modified: trunk/refman-4.1/optimization.xml
===================================================================
--- trunk/refman-4.1/optimization.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-4.1/optimization.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 2, Lines Added: 8, Lines Deleted: 9; 1885 bytes

@@ -133,7 +133,7 @@
           <para>
             If you insert an inappropriate or out-of-range value into a
             column, MySQL sets the column to the <quote>best possible
-            value</quote> instead of reporting an error. For numerical
+            value</quote> instead of reporting an error. For numeric
             values, this is 0, the smallest possible value or the
             largest possible value. For strings, this is either the
             empty string or as much of the string as can be stored in

@@ -5220,14 +5220,13 @@
 
         <listitem>
           <para>
-            If you are using numerical data, it is faster in many cases
-            to access information from a database (using a live
-            connection) than to access a text file. Information in the
-            database is likely to be stored in a more compact format
-            than in the text file, so accessing it involves fewer disk
-            accesses. You also save code in your application because you
-            need not parse your text files to find line and column
-            boundaries.
+            If you are using numeric data, it is faster in many cases to
+            access information from a database (using a live connection)
+            than to access a text file. Information in the database is
+            likely to be stored in a more compact format than in the
+            text file, so accessing it involves fewer disk accesses. You
+            also save code in your application because you need not
+            parse your text files to find line and column boundaries.
           </para>
         </listitem>
 


Modified: trunk/refman-4.1/tutorial.xml
===================================================================
--- trunk/refman-4.1/tutorial.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-4.1/tutorial.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 608 bytes

@@ -4183,7 +4183,7 @@
 
           <para>
             We want to sort on the concatenated <literal>id</literal>
-            and <literal>tvab</literal> in numerical order. Adding
+            and <literal>tvab</literal> in numeric order. Adding
             <literal>0</literal> to the result causes MySQL to treat the
             result as a number.
           </para>


Modified: trunk/refman-5.0/data-types.xml
===================================================================
--- trunk/refman-5.0/data-types.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-5.0/data-types.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 2, Lines Added: 3, Lines Deleted: 3; 1224 bytes

@@ -5170,8 +5170,8 @@
             present in the list of permitted values), the empty string
             is inserted instead as a special error value. This string
             can be distinguished from a <quote>normal</quote> empty
-            string by the fact that this string has the numerical value
-            0. More about this later.
+            string by the fact that this string has the numeric value 0.
+            More about this later.
           </para>
 
           <para>

@@ -5371,7 +5371,7 @@
         The empty string sorts before nonempty strings, and
         <literal>NULL</literal> values sort before all other enumeration
         values. To prevent unexpected results, specify the
-        <literal role="type">ENUM</literal> list in alphabetical order.
+        <literal role="type">ENUM</literal> list in alphabetic order.
         You can also use <literal>ORDER BY
         CAST(<replaceable>col</replaceable> AS CHAR)</literal> or
         <literal>ORDER BY


Modified: trunk/refman-5.0/information-schema.xml
===================================================================
--- trunk/refman-5.0/information-schema.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-5.0/information-schema.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 620 bytes

@@ -97,7 +97,7 @@
 
   <para>
     Explanation: The statement requests a list of all the tables in
-    database <literal>db5</literal>, in reverse alphabetical order,
+    database <literal>db5</literal>, in reverse alphabetic order,
     showing just three pieces of information: the name of the table, its
     type, and its storage engine.
   </para>


Modified: trunk/refman-5.0/optimization.xml
===================================================================
--- trunk/refman-5.0/optimization.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-5.0/optimization.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 2, Lines Added: 8, Lines Deleted: 9; 1885 bytes

@@ -133,7 +133,7 @@
           <para>
             If you insert an inappropriate or out-of-range value into a
             column, MySQL sets the column to the <quote>best possible
-            value</quote> instead of reporting an error. For numerical
+            value</quote> instead of reporting an error. For numeric
             values, this is 0, the smallest possible value or the
             largest possible value. For strings, this is either the
             empty string or as much of the string as can be stored in

@@ -7552,14 +7552,13 @@
 
         <listitem>
           <para>
-            If you are using numerical data, it is faster in many cases
-            to access information from a database (using a live
-            connection) than to access a text file. Information in the
-            database is likely to be stored in a more compact format
-            than in the text file, so accessing it involves fewer disk
-            accesses. You also save code in your application because you
-            need not parse your text files to find line and column
-            boundaries.
+            If you are using numeric data, it is faster in many cases to
+            access information from a database (using a live connection)
+            than to access a text file. Information in the database is
+            likely to be stored in a more compact format than in the
+            text file, so accessing it involves fewer disk accesses. You
+            also save code in your application because you need not
+            parse your text files to find line and column boundaries.
           </para>
         </listitem>
 


Modified: trunk/refman-5.0/tutorial.xml
===================================================================
--- trunk/refman-5.0/tutorial.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-5.0/tutorial.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 608 bytes

@@ -4139,7 +4139,7 @@
 
           <para>
             We want to sort on the concatenated <literal>id</literal>
-            and <literal>tvab</literal> in numerical order. Adding
+            and <literal>tvab</literal> in numeric order. Adding
             <literal>0</literal> to the result causes MySQL to treat the
             result as a number.
           </para>


Modified: trunk/refman-5.1/data-types.xml
===================================================================
--- trunk/refman-5.1/data-types.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-5.1/data-types.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 2, Lines Added: 3, Lines Deleted: 3; 1224 bytes

@@ -4896,8 +4896,8 @@
             present in the list of permitted values), the empty string
             is inserted instead as a special error value. This string
             can be distinguished from a <quote>normal</quote> empty
-            string by the fact that this string has the numerical value
-            0. More about this later.
+            string by the fact that this string has the numeric value 0.
+            More about this later.
           </para>
 
           <para>

@@ -5097,7 +5097,7 @@
         The empty string sorts before nonempty strings, and
         <literal>NULL</literal> values sort before all other enumeration
         values. To prevent unexpected results, specify the
-        <literal role="type">ENUM</literal> list in alphabetical order.
+        <literal role="type">ENUM</literal> list in alphabetic order.
         You can also use <literal>ORDER BY
         CAST(<replaceable>col</replaceable> AS CHAR)</literal> or
         <literal>ORDER BY


Modified: trunk/refman-5.1/functions-core.xml
===================================================================
--- trunk/refman-5.1/functions-core.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-5.1/functions-core.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 797 bytes

@@ -15036,9 +15036,9 @@
 
       <listitem>
         <para>
-          Test numerical data for out of range values; truncate, round,
-          or reject values that are out of range. Test strings for
-          illegal characters and either strip them out or reject input
+          Test numeric data for out of range values; truncate, round, or
+          reject values that are out of range. Test strings for illegal
+          characters and either strip them out or reject input
           containing them.
         </para>
       </listitem>


Modified: trunk/refman-5.1/information-schema.xml
===================================================================
--- trunk/refman-5.1/information-schema.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-5.1/information-schema.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 620 bytes

@@ -97,7 +97,7 @@
 
   <para>
     Explanation: The statement requests a list of all the tables in
-    database <literal>db5</literal>, in reverse alphabetical order,
+    database <literal>db5</literal>, in reverse alphabetic order,
     showing just three pieces of information: the name of the table, its
     type, and its storage engine.
   </para>


Modified: trunk/refman-5.1/optimization.xml
===================================================================
--- trunk/refman-5.1/optimization.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-5.1/optimization.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 2, Lines Added: 8, Lines Deleted: 9; 1885 bytes

@@ -133,7 +133,7 @@
           <para>
             If you insert an inappropriate or out-of-range value into a
             column, MySQL sets the column to the <quote>best possible
-            value</quote> instead of reporting an error. For numerical
+            value</quote> instead of reporting an error. For numeric
             values, this is 0, the smallest possible value or the
             largest possible value. For strings, this is either the
             empty string or as much of the string as can be stored in

@@ -8413,14 +8413,13 @@
 
         <listitem>
           <para>
-            If you are using numerical data, it is faster in many cases
-            to access information from a database (using a live
-            connection) than to access a text file. Information in the
-            database is likely to be stored in a more compact format
-            than in the text file, so accessing it involves fewer disk
-            accesses. You also save code in your application because you
-            need not parse your text files to find line and column
-            boundaries.
+            If you are using numeric data, it is faster in many cases to
+            access information from a database (using a live connection)
+            than to access a text file. Information in the database is
+            likely to be stored in a more compact format than in the
+            text file, so accessing it involves fewer disk accesses. You
+            also save code in your application because you need not
+            parse your text files to find line and column boundaries.
           </para>
         </listitem>
 


Modified: trunk/refman-5.1/tutorial.xml
===================================================================
--- trunk/refman-5.1/tutorial.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-5.1/tutorial.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 608 bytes

@@ -4126,7 +4126,7 @@
 
           <para>
             We want to sort on the concatenated <literal>id</literal>
-            and <literal>tvab</literal> in numerical order. Adding
+            and <literal>tvab</literal> in numeric order. Adding
             <literal>0</literal> to the result causes MySQL to treat the
             result as a number.
           </para>


Modified: trunk/refman-5.5/data-types.xml
===================================================================
--- trunk/refman-5.5/data-types.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-5.5/data-types.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 2, Lines Added: 3, Lines Deleted: 3; 1224 bytes

@@ -4909,8 +4909,8 @@
             present in the list of permitted values), the empty string
             is inserted instead as a special error value. This string
             can be distinguished from a <quote>normal</quote> empty
-            string by the fact that this string has the numerical value
-            0. More about this later.
+            string by the fact that this string has the numeric value 0.
+            More about this later.
           </para>
 
           <para>

@@ -5110,7 +5110,7 @@
         The empty string sorts before nonempty strings, and
         <literal>NULL</literal> values sort before all other enumeration
         values. To prevent unexpected results, specify the
-        <literal role="type">ENUM</literal> list in alphabetical order.
+        <literal role="type">ENUM</literal> list in alphabetic order.
         You can also use <literal>ORDER BY
         CAST(<replaceable>col</replaceable> AS CHAR)</literal> or
         <literal>ORDER BY


Modified: trunk/refman-5.5/functions-core.xml
===================================================================
--- trunk/refman-5.5/functions-core.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-5.5/functions-core.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 797 bytes

@@ -15275,9 +15275,9 @@
 
       <listitem>
         <para>
-          Test numerical data for out of range values; truncate, round,
-          or reject values that are out of range. Test strings for
-          illegal characters and either strip them out or reject input
+          Test numeric data for out of range values; truncate, round, or
+          reject values that are out of range. Test strings for illegal
+          characters and either strip them out or reject input
           containing them.
         </para>
       </listitem>


Modified: trunk/refman-5.5/information-schema.xml
===================================================================
--- trunk/refman-5.5/information-schema.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-5.5/information-schema.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 620 bytes

@@ -97,7 +97,7 @@
 
   <para>
     Explanation: The statement requests a list of all the tables in
-    database <literal>db5</literal>, in reverse alphabetical order,
+    database <literal>db5</literal>, in reverse alphabetic order,
     showing just three pieces of information: the name of the table, its
     type, and its storage engine.
   </para>


Modified: trunk/refman-5.5/optimization.xml
===================================================================
--- trunk/refman-5.5/optimization.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-5.5/optimization.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 2, Lines Added: 8, Lines Deleted: 9; 1885 bytes

@@ -133,7 +133,7 @@
           <para>
             If you insert an inappropriate or out-of-range value into a
             column, MySQL sets the column to the <quote>best possible
-            value</quote> instead of reporting an error. For numerical
+            value</quote> instead of reporting an error. For numeric
             values, this is 0, the smallest possible value or the
             largest possible value. For strings, this is either the
             empty string or as much of the string as can be stored in

@@ -8531,14 +8531,13 @@
 
         <listitem>
           <para>
-            If you are using numerical data, it is faster in many cases
-            to access information from a database (using a live
-            connection) than to access a text file. Information in the
-            database is likely to be stored in a more compact format
-            than in the text file, so accessing it involves fewer disk
-            accesses. You also save code in your application because you
-            need not parse your text files to find line and column
-            boundaries.
+            If you are using numeric data, it is faster in many cases to
+            access information from a database (using a live connection)
+            than to access a text file. Information in the database is
+            likely to be stored in a more compact format than in the
+            text file, so accessing it involves fewer disk accesses. You
+            also save code in your application because you need not
+            parse your text files to find line and column boundaries.
           </para>
         </listitem>
 


Modified: trunk/refman-5.5/tutorial.xml
===================================================================
--- trunk/refman-5.5/tutorial.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-5.5/tutorial.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 608 bytes

@@ -4126,7 +4126,7 @@
 
           <para>
             We want to sort on the concatenated <literal>id</literal>
-            and <literal>tvab</literal> in numerical order. Adding
+            and <literal>tvab</literal> in numeric order. Adding
             <literal>0</literal> to the result causes MySQL to treat the
             result as a number.
           </para>


Modified: trunk/refman-6.0/data-types.xml
===================================================================
--- trunk/refman-6.0/data-types.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-6.0/data-types.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 2, Lines Added: 3, Lines Deleted: 3; 1224 bytes

@@ -4910,8 +4910,8 @@
             present in the list of permitted values), the empty string
             is inserted instead as a special error value. This string
             can be distinguished from a <quote>normal</quote> empty
-            string by the fact that this string has the numerical value
-            0. More about this later.
+            string by the fact that this string has the numeric value 0.
+            More about this later.
           </para>
 
           <para>

@@ -5111,7 +5111,7 @@
         The empty string sorts before nonempty strings, and
         <literal>NULL</literal> values sort before all other enumeration
         values. To prevent unexpected results, specify the
-        <literal role="type">ENUM</literal> list in alphabetical order.
+        <literal role="type">ENUM</literal> list in alphabetic order.
         You can also use <literal>ORDER BY
         CAST(<replaceable>col</replaceable> AS CHAR)</literal> or
         <literal>ORDER BY


Modified: trunk/refman-6.0/functions-core.xml
===================================================================
--- trunk/refman-6.0/functions-core.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-6.0/functions-core.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 797 bytes

@@ -15608,9 +15608,9 @@
 
       <listitem>
         <para>
-          Test numerical data for out of range values; truncate, round,
-          or reject values that are out of range. Test strings for
-          illegal characters and either strip them out or reject input
+          Test numeric data for out of range values; truncate, round, or
+          reject values that are out of range. Test strings for illegal
+          characters and either strip them out or reject input
           containing them.
         </para>
       </listitem>


Modified: trunk/refman-6.0/information-schema.xml
===================================================================
--- trunk/refman-6.0/information-schema.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-6.0/information-schema.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 620 bytes

@@ -97,7 +97,7 @@
 
   <para>
     Explanation: The statement requests a list of all the tables in
-    database <literal>db5</literal>, in reverse alphabetical order,
+    database <literal>db5</literal>, in reverse alphabetic order,
     showing just three pieces of information: the name of the table, its
     type, and its storage engine.
   </para>


Modified: trunk/refman-6.0/optimization.xml
===================================================================
--- trunk/refman-6.0/optimization.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-6.0/optimization.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 2, Lines Added: 8, Lines Deleted: 9; 1885 bytes

@@ -133,7 +133,7 @@
           <para>
             If you insert an inappropriate or out-of-range value into a
             column, MySQL sets the column to the <quote>best possible
-            value</quote> instead of reporting an error. For numerical
+            value</quote> instead of reporting an error. For numeric
             values, this is 0, the smallest possible value or the
             largest possible value. For strings, this is either the
             empty string or as much of the string as can be stored in

@@ -9617,14 +9617,13 @@
 
         <listitem>
           <para>
-            If you are using numerical data, it is faster in many cases
-            to access information from a database (using a live
-            connection) than to access a text file. Information in the
-            database is likely to be stored in a more compact format
-            than in the text file, so accessing it involves fewer disk
-            accesses. You also save code in your application because you
-            need not parse your text files to find line and column
-            boundaries.
+            If you are using numeric data, it is faster in many cases to
+            access information from a database (using a live connection)
+            than to access a text file. Information in the database is
+            likely to be stored in a more compact format than in the
+            text file, so accessing it involves fewer disk accesses. You
+            also save code in your application because you need not
+            parse your text files to find line and column boundaries.
           </para>
         </listitem>
 


Modified: trunk/refman-6.0/tutorial.xml
===================================================================
--- trunk/refman-6.0/tutorial.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-6.0/tutorial.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 608 bytes

@@ -4126,7 +4126,7 @@
 
           <para>
             We want to sort on the concatenated <literal>id</literal>
-            and <literal>tvab</literal> in numerical order. Adding
+            and <literal>tvab</literal> in numeric order. Adding
             <literal>0</literal> to the result causes MySQL to treat the
             result as a number.
           </para>


Modified: trunk/refman-common/connector-j.xml
===================================================================
--- trunk/refman-common/connector-j.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-common/connector-j.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 743 bytes

@@ -1757,9 +1757,9 @@
 
       <para>
         In general, any MySQL data type can be converted to a
-        java.lang.String, and any numerical type can be converted to any
-        of the Java numerical types, although round-off, overflow, or
-        loss of precision may occur.
+        java.lang.String, and any numeric type can be converted to any
+        of the Java numeric types, although round-off, overflow, or loss
+        of precision may occur.
       </para>
 
       <para>


Modified: trunk/refman-common/connector-net-programming.xml
===================================================================
--- trunk/refman-common/connector-net-programming.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-common/connector-net-programming.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 685 bytes

@@ -2113,7 +2113,7 @@
 
       <para>
         It is important to order the
-        <literal role="stmt">SELECT</literal> queries in alphabetical
+        <literal role="stmt">SELECT</literal> queries in alphabetic
         order, as this is the order the report will expect its source
         tables to be in. One SetDataSource statement is needed for each
         table in the report.


Modified: trunk/refman-common/connector-net-ref.xml
===================================================================
--- trunk/refman-common/connector-net-ref.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-common/connector-net-ref.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 676 bytes

@@ -15503,7 +15503,7 @@
             <tbody>
               <row>
                 <entry>HResult(inherited from Exception)</entry>
-                <entry>Gets or sets HRESULT, a coded numerical value that is assigned to a
+                <entry>Gets or sets HRESULT, a coded numeric value that is assigned to a
                   specific exception.</entry>
               </row>
             </tbody>


Modified: trunk/refman-common/connector-odbc.xml
===================================================================
--- trunk/refman-common/connector-odbc.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-common/connector-odbc.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 725 bytes

@@ -7980,7 +7980,7 @@
 
           <para>
             If you have problems importing data into Microsoft Excel,
-            particularly numerical, date, and time values, this is
+            particularly numeric, date, and time values, this is
             probably because of a bug in Excel, where the column type of
             the source data is used to determine the data type when that
             data is inserted into a cell within the worksheet. The


Modified: trunk/refman-common/news-innodb.xml
===================================================================
--- trunk/refman-common/news-innodb.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/refman-common/news-innodb.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 715 bytes

@@ -799,7 +799,7 @@
         <para>
           Fixed a bug: in a <literal>FOREIGN KEY</literal>, <literal>ON
           UPDATE CASCADE</literal> was not triggered if the update
-          changed a string to another value identical in alphabetical
+          changed a string to another value identical in alphabetic
           ordering, for example, <quote><literal>abc</literal></quote>
           -&gt; <quote><literal>aBc</literal></quote>.
         </para>


Modified: trunk/sample-data/sakila/sakila.xml
===================================================================
--- trunk/sample-data/sakila/sakila.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/sample-data/sakila/sakila.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 1103 bytes

@@ -298,7 +298,7 @@
 
       <para>
         The following sections describe the tables that make up the
-        &sampdb; sample database, in alphabetical order.
+        &sampdb; sample database, in alphabetic order.
       </para>
 
       <section id="sakila-structure-tables-actor">

@@ -1400,7 +1400,7 @@
 
       <para>
         The following sections describe the views that are included with
-        the &sampdb; sample database, in alphabetical order.
+        the &sampdb; sample database, in alphabetic order.
       </para>
 
       <section id="sakila-structure-views-actor_info">

@@ -1571,7 +1571,7 @@
 
       <para>
         The following sections describe the stored procedures included
-        with the &sampdb; sample database, in alphabetical order.
+        with the &sampdb; sample database, in alphabetic order.
       </para>
 
       <para>


Modified: trunk/workbench/table-editor.xml
===================================================================
--- trunk/workbench/table-editor.xml	2010-07-28 16:50:05 UTC (rev 21949)
+++ trunk/workbench/table-editor.xml	2010-07-28 19:27:14 UTC (rev 21950)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 831 bytes

@@ -336,7 +336,7 @@
         manually add single quote characters for the default value. Note
         that &workbench; will <emphasis role="bold">not</emphasis>
         prevent you from entering the default value without the single
-        quotation marks. If a non-numerical default value is entered
+        quotation marks. If a non-numeric default value is entered
         without quotation marks, this will lead to errors. For example,
         if the model is reverse engineered, the script will contain
         unquoted default values for <literal>ENUM</literal> columns and


Thread
svn commit - mysqldoc@docsrva: r21950 - in trunk: . dynamic-docs/changelog innodb-plugin-1.0 innodb-plugin-1.1 mysql-monitor-common mysqltest-1.0 mysq...paul.dubois28 Jul