From: jon
Date: August 30 2006 1:17am
Subject: svn commit - mysqldoc@docsrva: r3138 - trunk/ndbapi
List-Archive: http://lists.mysql.com/commits/11054
Message-Id: <200608300117.k7U1HMSL008732@docsrva.mysql.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Author: jstephens
Date: 2006-08-30 03:17:20 +0200 (Wed, 30 Aug 2006)
New Revision: 3138

Log:
Reformat.

Modified:
   trunk/ndbapi/ndb-classes.xml


Modified: trunk/ndbapi/ndb-classes.xml
===================================================================
--- trunk/ndbapi/ndb-classes.xml	2006-08-30 01:14:52 UTC (rev 3137)
+++ trunk/ndbapi/ndb-classes.xml	2006-08-30 01:17:20 UTC (rev 3138)
Changed blocks: 9, Lines Added: 24, Lines Deleted: 24; 4982 bytes

@@ -12,8 +12,8 @@
   <abstract>
 
     <para>
-      This chapter provides a detailed listing of all public <literal>NDB</literal> API
-      classes.
+      This chapter provides a detailed listing of all public
+      <literal>NDB</literal> API classes.
     </para>
 
     <para>

@@ -83,14 +83,15 @@
       <title>Description</title>
 
       <para>
-        Any non-trivial <literal>NDB</literal> API program makes use of at least one
-        instance of <literal>Ndb</literal>. By using several
-        <literal>Ndb</literal> objects, it is possible to implement a
-        multi-threaded application. You should remember that one
-        <literal>Ndb</literal> object cannot be shared between threads;
-        however, it is possible for a single thread to use multiple
-        <literal>Ndb</literal> objects. A single application process can
-        support a maximum of 128 <literal>Ndb</literal> objects.
+        Any non-trivial <literal>NDB</literal> API program makes use of
+        at least one instance of <literal>Ndb</literal>. By using
+        several <literal>Ndb</literal> objects, it is possible to
+        implement a multi-threaded application. You should remember that
+        one <literal>Ndb</literal> object cannot be shared between
+        threads; however, it is possible for a single thread to use
+        multiple <literal>Ndb</literal> objects. A single application
+        process can support a maximum of 128 <literal>Ndb</literal>
+        objects.
       </para>
 
     </formalpara>

@@ -250,10 +251,10 @@
 
           <para>
             This creates an instance of <literal>Ndb</literal>, which
-            represents a connection to the MySQL Cluster. All <literal>NDB</literal> API
-            applications should begin with the creation of at least one
-            <literal>Ndb</literal> object. This requires the creation of
-            at least one instance of
+            represents a connection to the MySQL Cluster. All
+            <literal>NDB</literal> API applications should begin with
+            the creation of at least one <literal>Ndb</literal> object.
+            This requires the creation of at least one instance of
             <literal>Ndb_cluster_connection</literal>, which serves as a
             container for a cluster connectstring.
           </para>

@@ -942,8 +943,8 @@
           <title>Description</title>
 
           <para>
-            This is one of two <literal>NDB</literal> API methods provided for closing a
-            transaction (the other being
+            This is one of two <literal>NDB</literal> API methods
+            provided for closing a transaction (the other being
             <literal>NdbTransaction::close()</literal> &mdash; see
             <xref linkend="class-ndbtransaction-close"/>). You must call
             one of these two methods to close the transaction once it

@@ -1399,7 +1400,8 @@
             This method provides you with two different ways to obtain
             an <literal>NdbError</literal> object representing an error
             condition. For more detailed information about error
-            handling in the <literal>NDB</literal> API, see <xref linkend="errors"/>.
+            handling in the <literal>NDB</literal> API, see
+            <xref linkend="errors"/>.
           </para>
 
         </formalpara>

@@ -1447,8 +1449,8 @@
             obtain the error matching a specific
             <replaceable>errorCode</replaceable>, invoke the method
             passing the code (an <literal>int</literal>) to it as a
-            parameter. For a listing of <literal>NDB</literal> API error codes and
-            corresponding error messages, see
+            parameter. For a listing of <literal>NDB</literal> API error
+            codes and corresponding error messages, see
             <xref
             linkend="ndb-error-messages"/>.
           </para>

@@ -3301,8 +3303,7 @@
           <para>
             A reference to an integer <replaceable>isNull</replaceable>.
             Following invocation, this parameter has one of the
-            following values, interpreted as shown here: 
-            
+            following values, interpreted as shown here:
 
             <itemizedlist>
 

@@ -4533,7 +4534,7 @@
 
     </formalpara>
 
-    <warning>      
+    <warning>
       <para>
         Tables and indexes created using
         <literal>NdbDictionary</literal> cannot be viewed from the MySQL

@@ -4547,10 +4548,9 @@
         been dropped using the <literal>NDB</literal> API will no longer
         be usable by MySQL following such operations. In this event, the
         table must be dropped, and then re-created using MySQL to make
-        it accessible to MySQL once more. 
+        it accessible to MySQL once more.
       </para>
     </warning>
-    
 
     <formalpara>