List:Commits« Previous MessageNext Message »
From:jon Date:April 25 2007 7:12am
Subject:svn commit - mysqldoc@docsrva: r6173 - trunk/refman-5.1
View as plain text  
Author: jstephens
Date: 2007-04-25 09:12:45 +0200 (Wed, 25 Apr 2007)
New Revision: 6173

Log:

Reformat.



Modified:
   trunk/refman-5.1/mysql-cluster-mccge.xml


Modified: trunk/refman-5.1/mysql-cluster-mccge.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-mccge.xml	2007-04-25 07:09:12 UTC (rev 6172)
+++ trunk/refman-5.1/mysql-cluster-mccge.xml	2007-04-25 07:12:45 UTC (rev 6173)
Changed blocks: 14, Lines Added: 53, Lines Deleted: 47; 10150 bytes

@@ -55,9 +55,9 @@
   </indexterm>
 
   <para>
-    MySQL &current-series-mccge; is currently available and supported on a
-    number of platforms, including Linux, Solaris, Mac OS X, BSD, HP-UX,
-    and many other Unix-style operating systems on a variety of
+    MySQL &current-series-mccge; is currently available and supported on
+    a number of platforms, including Linux, Solaris, Mac OS X, BSD,
+    HP-UX, and many other Unix-style operating systems on a variety of
     hardware. For exact levels of support available for on specific
     combinations of operating system versions, operating system
     distributions, and hardware platforms, please refer to the

@@ -67,16 +67,18 @@
   </para>
 
   <para>
-    Like the standard version of MySQL Cluster, MySQL &current-series-mccge;
-    is <emphasis>not</emphasis> currently supported on Microsoft
-    Windows. We are working to make MySQL Cluster available on all
-    operating systems supported by MySQL, including Windows.
+    Like the standard version of MySQL Cluster, MySQL
+    &current-series-mccge; is <emphasis>not</emphasis> currently
+    supported on Microsoft Windows. We are working to make MySQL Cluster
+    available on all operating systems supported by MySQL, including
+    Windows.
   </para>
 
   <para>
     This chapter represents a work in progress, and its contents are
-    subject to revision as MySQL &current-series-mccge; continues to evolve.
-    Additional information can be found on the MySQL AB web site at
+    subject to revision as MySQL &current-series-mccge; continues to
+    evolve. Additional information can be found on the MySQL AB web site
+    at
     <ulink url="http://www.mysql.com/products/database/clustercge/"/>.
   </para>
 

@@ -974,8 +976,8 @@
         applications, or configuration to support MySQL Cluster. For
         supported operating systems, a standard installation should be
         sufficient. The MySQL software requirements are simple: all that
-        is needed is to build the server from the MySQL &current-series-mccge;
-        source code with the appropriate options.
+        is needed is to build the server from the MySQL
+        &current-series-mccge; source code with the appropriate options.
       </para>
 
       <para>

@@ -2131,9 +2133,9 @@
       </indexterm>
 
       <para>
-        When building MySQL &current-series-mccge; from source, be sure to use
-        the <option>--with-ndbcluster</option> option when running
-        <command>configure</command>. You can also use the
+        When building MySQL &current-series-mccge; from source, be sure
+        to use the <option>--with-ndbcluster</option> option when
+        running <command>configure</command>. You can also use the
         <command>BUILD/compile-pentium-max</command> build script;
         however, you will very likely wish to modify it to suit your
         local conditions.

@@ -2144,18 +2146,18 @@
           <command>BUILD/compile-pentium-max</command> by default builds
           the MySQL Server with support for the
           <literal>InnoDB</literal> storage engine. <emphasis>You must
-          not deploy or make use of MySQL &current-series-mccge; employing the
-          <literal>InnoDB</literal> storage engine without prior written
-          permission to do so from MySQL AB</emphasis>.
+          not deploy or make use of MySQL &current-series-mccge;
+          employing the <literal>InnoDB</literal> storage engine without
+          prior written permission to do so from MySQL AB</emphasis>.
         </para>
 
         <para>
           If you wish to use <literal>InnoDB</literal> technology in
-          conjunction with your use of MySQL &current-series-mccge; and do not
-          already have authorization to do so as part of your MySQL
-          Server license, contact your MySQL AB salesperson or other
-          authorized MySQL AB representative for assistance in upgrading
-          your MySQL Server license.
+          conjunction with your use of MySQL &current-series-mccge; and
+          do not already have authorization to do so as part of your
+          MySQL Server license, contact your MySQL AB salesperson or
+          other authorized MySQL AB representative for assistance in
+          upgrading your MySQL Server license.
         </para>
       </warning>
 

@@ -2796,9 +2798,10 @@
           <listitem>
             <para>
               <literal>[SHM]</literal>: Defines shared-memory
-              connections between nodes. In MySQL &current-series-mccge;, it
-              is enabled by default, but should still be considered
-              experimental. For a discussion of SHM interconnects, see
+              connections between nodes. In MySQL
+              &current-series-mccge;, it is enabled by default, but
+              should still be considered experimental. For a discussion
+              of SHM interconnects, see
               <xref linkend="mysql-cluster-shm-definition"/>.
             </para>
           </listitem>

@@ -4721,9 +4724,10 @@
             </para>
 
             <para>
-              This parameter is deprecated in MySQL &current-series-mccge;;
-              you should use <literal>MaxNoOfOrderedIndexes</literal>
-              and <literal>MaxNoOfUniqueHashIndexes</literal> instead.
+              This parameter is deprecated in MySQL
+              &current-series-mccge;; you should use
+              <literal>MaxNoOfOrderedIndexes</literal> and
+              <literal>MaxNoOfUniqueHashIndexes</literal> instead.
             </para>
 
             <para>

@@ -10746,9 +10750,9 @@
           </para>
 
           <para>
-            It is not possible in MySQL &current-series-mccge; for data nodes
-            to join the cluster while it is running in single user mode.
-            (See Bug #20395 for more information.)
+            It is not possible in MySQL &current-series-mccge; for data
+            nodes to join the cluster while it is running in single user
+            mode. (See Bug #20395 for more information.)
           </para>
         </listitem>
 

@@ -13699,9 +13703,9 @@
       applications using the <literal>NDB</literal> API. The source code
       for most of these programs may be found in the
       <filename>storage/ndb/tools</filename> directory of the MySQL
-      &current-series-mccge; tree (see <xref linkend="installing-source"/>).
-      The <literal>NDB</literal> API is not covered in this manual;
-      please refer to the
+      &current-series-mccge; tree (see
+      <xref linkend="installing-source"/>). The <literal>NDB</literal>
+      API is not covered in this manual; please refer to the
       <ulink url="&base-url-docs;/ndbapi/en/"><literal>NDB</literal> API
       Guide</ulink> for information about this API.
     </para>

@@ -17199,8 +17203,8 @@
         <important>
           <para>
             See <xref linkend="news-5-1-15-ndb-6-1-5"/>, before
-            upgrading from a previous &current-series-mccge; or mainline MySQL
-            5.1 release.
+            upgrading from a previous &current-series-mccge; or mainline
+            MySQL 5.1 release.
           </para>
         </important>
       </para>

@@ -19772,16 +19776,16 @@
 
     <para>
       In this section, we provide a list of known limitations in MySQL
-      Cluster releases in the &current-series-mccge;.x series compared to
-      features available when using the <literal>MyISAM</literal> and
+      Cluster releases in the &current-series-mccge;.x series compared
+      to features available when using the <literal>MyISAM</literal> and
       <literal>InnoDB</literal> storage engines. Currently, there are no
       plans to address these in coming releases of MySQL
-      &current-series-mccge;; however, we will attempt to supply fixes for
-      these issues in subsequent release series. If you check the
+      &current-series-mccge;; however, we will attempt to supply fixes
+      for these issues in subsequent release series. If you check the
       <quote>Cluster</quote> category in the MySQL bugs database at
       <ulink url="http://bugs.mysql.com"/>, you can find known bugs
-      which (if marked <quote>&current-series-mccge;</quote>) we intend to
-      correct in upcoming releases of MySQL &current-series-mccge;.
+      which (if marked <quote>&current-series-mccge;</quote>) we intend
+      to correct in upcoming releases of MySQL &current-series-mccge;.
     </para>
 
     <para>

@@ -19789,7 +19793,8 @@
       conditions just set forth. You can report any discrepancies that
       you encounter to the MySQL bugs database using the instructions
       given in <xref linkend="bug-reports"/>. If we do not plan to fix
-      the problem in MySQL &current-series-mccge;, we will add it to the list.
+      the problem in MySQL &current-series-mccge;, we will add it to the
+      list.
     </para>
 
     <para>

@@ -19861,8 +19866,9 @@
             <para>
               Geometry datatypes (<literal>WKT</literal> and
               <literal>WKB</literal>) are supported in
-              <literal>NDB</literal> tables in MySQL &current-series-mccge;.
-              However, spatial indexes are not supported.
+              <literal>NDB</literal> tables in MySQL
+              &current-series-mccge;. However, spatial indexes are not
+              supported.
             </para>
           </listitem>
 

@@ -20674,8 +20680,8 @@
               concurrently on a single host, it is not always advisable
               to do so for reasons of performance and high availability,
               as well as other considerations. In particular, we do not
-              in MySQL &current-series-mccge; support for production use any
-              MySQL Cluster deployment in which more than one
+              in MySQL &current-series-mccge; support for production use
+              any MySQL Cluster deployment in which more than one
               <command>ndbd</command> process is run on a single
               physical machine.
             </para>


Thread
svn commit - mysqldoc@docsrva: r6173 - trunk/refman-5.1jon25 Apr