List:Commits« Previous MessageNext Message »
From:jon Date:May 22 2007 4:23am
Subject:svn commit - mysqldoc@docsrva: r6558 - in trunk: refman-4.1 refman-5.0 refman-5.1
View as plain text  
Author: jstephens
Date: 2007-05-22 06:23:07 +0200 (Tue, 22 May 2007)
New Revision: 6558

Log:

Reformat.



Modified:
   trunk/refman-4.1/mysql-cluster.xml
   trunk/refman-5.0/mysql-cluster.xml
   trunk/refman-5.1/mysql-cluster.xml


Modified: trunk/refman-4.1/mysql-cluster.xml
===================================================================
--- trunk/refman-4.1/mysql-cluster.xml	2007-05-22 04:22:01 UTC (rev 6557)
+++ trunk/refman-4.1/mysql-cluster.xml	2007-05-22 04:23:07 UTC (rev 6558)
Changed blocks: 4, Lines Added: 64, Lines Deleted: 64; 5675 bytes

@@ -392,7 +392,7 @@
     <para>
       (However, it should be noted MySQL does not currently support the
       use of multiple data nodes on a single computer in a production
-      setting. See 
+      setting. See
       <xref linkend="mysql-cluster-limitations-multiple-nodes"/>.)
     </para>
 

@@ -17784,7 +17784,7 @@
                 transaction isolation level. (<literal>InnoDB</literal>,
                 for example, supports <literal>READ COMMITTED</literal>,
                 <literal>READ UNCOMMITTED</literal>, <literal>REPEATABLE
-                  READ</literal>, and <literal>SERIALIZABLE</literal>.)
+                READ</literal>, and <literal>SERIALIZABLE</literal>.)
                 See
                 <xref linkend="mysql-cluster-backup-troubleshooting"/>,
                 for information on how this can affect backing up and

@@ -18092,85 +18092,84 @@
         <secondary>unsupported features</secondary>
       </indexterm>
 
-      
+      <para>
+        A number of features supported by other storage engines are not
+        supported for <literal>NDB</literal> tables. Trying to use any
+        of these features in MySQL Cluster does not cause errors in or
+        of itself; however, errors may occur in applications that
+        expects the features to be supported or enforced:
 
-        <para>
-          A number of features supported by other storage engines are
-          not supported for <literal>NDB</literal> tables. Trying to use
-          any of these features in MySQL Cluster does not cause errors
-          in or of itself; however, errors may occur in applications
-          that expects the features to be supported or enforced:
+        <itemizedlist>
 
-          <itemizedlist>
+          <listitem>
+            <formalpara>
 
-            <listitem>
-              <formalpara>
+              <title>Foreign key constraints</title>
 
-                <title>Foreign key constraints</title>
+              <para>
+                The foreign key construct is ignored, just as it is in
+                <literal>MyISAM</literal> tables.
+              </para>
 
-                <para>
-                  The foreign key construct is ignored, just as it is in
-                  <literal>MyISAM</literal> tables.
-                </para>
+            </formalpara>
+          </listitem>
 
-              </formalpara>
-            </listitem>
+          <listitem>
+            <formalpara>
 
-            <listitem>
-              <formalpara>
+              <title><literal>OPTIMIZE</literal> operations</title>
 
-                <title><literal>OPTIMIZE</literal> operations</title>
+              <para>
+                <literal>OPTIMIZE</literal> operations are not
+                supported.
+              </para>
 
-                <para>
-                  <literal>OPTIMIZE</literal> operations are not
-                  supported.
-                </para>
+            </formalpara>
+          </listitem>
 
-              </formalpara>
-            </listitem>
+          <listitem>
+            <formalpara>
 
-            <listitem>
-              <formalpara>
+              <title><literal>LOAD TABLE ... FROM MASTER</literal></title>
 
-                <title><literal>LOAD TABLE ... FROM MASTER</literal></title>
+              <para>
+                <literal>LOAD TABLE ... FROM MASTER</literal> is not
+                supported.
+              </para>
 
-                <para>
-                  <literal>LOAD TABLE ... FROM MASTER</literal> is not
-                  supported.
-                </para>
+            </formalpara>
+          </listitem>
 
-              </formalpara>
-            </listitem>
-            
-            <listitem>
-              <formalpara>
-                
-                <title>Savepoints and rollbacks</title>
-                
-                <para>
-                  Savepoints and rollbacks to savepoints are ignored as
-                  in <literal>MyISAM</literal>.
-                </para>
-                
-              </formalpara>
-            </listitem>
+          <listitem>
+            <formalpara>
 
-      <listitem>
-              <formalpara>
+              <title>Savepoints and rollbacks</title>
 
-                <title>Durability of commits</title>
+              <para>
+                Savepoints and rollbacks to savepoints are ignored as in
+                <literal>MyISAM</literal>.
+              </para>
 
-                <para>
-                  There are no durable commits on disk. Commits are replicated,
-                  but there is no guarantee that logs are flushed to
-                  disk on commit.
-                </para>
+            </formalpara>
+          </listitem>
 
-              </formalpara>
-      </listitem>
-          </itemizedlist>
-        </para>
-      
+          <listitem>
+            <formalpara>
+
+              <title>Durability of commits</title>
+
+              <para>
+                There are no durable commits on disk. Commits are
+                replicated, but there is no guarantee that logs are
+                flushed to disk on commit.
+              </para>
+
+            </formalpara>
+          </listitem>
+
+        </itemizedlist>
+      </para>
+
       <note>
         <para>
           See <xref linkend="mysql-cluster-limitations-transactions"/>,

@@ -18442,7 +18441,8 @@
           </listitem>
 
         </itemizedlist>
-        See also 
+
+        See also
         <xref linkend="mysql-cluster-limitations-multiple-nodes"/>.
       </para>
 


Modified: trunk/refman-5.0/mysql-cluster.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster.xml	2007-05-22 04:22:01 UTC (rev 6557)
+++ trunk/refman-5.0/mysql-cluster.xml	2007-05-22 04:23:07 UTC (rev 6558)
Changed blocks: 5, Lines Added: 41, Lines Deleted: 41; 4850 bytes

@@ -313,7 +313,7 @@
     <para>
       (However, it should be noted MySQL does not currently support the
       use of multiple data nodes on a single computer in a production
-      setting. See 
+      setting. See
       <xref linkend="mysql-cluster-limitations-multiple-nodes"/>.)
     </para>
 

@@ -17884,7 +17884,7 @@
                 transaction isolation level. (<literal>InnoDB</literal>,
                 for example, supports <literal>READ COMMITTED</literal>,
                 <literal>READ UNCOMMITTED</literal>, <literal>REPEATABLE
-                  READ</literal>, and <literal>SERIALIZABLE</literal>.)
+                READ</literal>, and <literal>SERIALIZABLE</literal>.)
                 See
                 <xref linkend="mysql-cluster-backup-troubleshooting"/>,
                 for information on how this can affect backing up and

@@ -18184,93 +18184,92 @@
     </section>
 
     <section id="mysql-cluster-limitations-unsupported-missing">
-      
+
       <title>Unsupported Or Missing Features</title>
-      
+
       <indexterm>
         <primary>MySQL Cluster limitations</primary>
         <secondary>unsupported features</secondary>
       </indexterm>
-      
-      
-      
+
       <para>
-        A number of features supported by other storage engines are
-        not supported for <literal>NDB</literal> tables. Trying to use
-        any of these features in MySQL Cluster does not cause errors
-        in or of itself; however, errors may occur in applications
-        that expects the features to be supported or enforced:
-        
+        A number of features supported by other storage engines are not
+        supported for <literal>NDB</literal> tables. Trying to use any
+        of these features in MySQL Cluster does not cause errors in or
+        of itself; however, errors may occur in applications that
+        expects the features to be supported or enforced:
+
         <itemizedlist>
-          
+
           <listitem>
             <formalpara>
-              
+
               <title>Foreign key constraints</title>
-              
+
               <para>
                 The foreign key construct is ignored, just as it is in
                 <literal>MyISAM</literal> tables.
               </para>
-              
+
             </formalpara>
           </listitem>
-          
+
           <listitem>
             <formalpara>
-              
+
               <title><literal>OPTIMIZE</literal> operations</title>
-              
+
               <para>
                 <literal>OPTIMIZE</literal> operations are not
                 supported.
               </para>
-              
+
             </formalpara>
           </listitem>
-          
+
           <listitem>
             <formalpara>
-              
+
               <title><literal>LOAD TABLE ... FROM MASTER</literal></title>
-              
+
               <para>
                 <literal>LOAD TABLE ... FROM MASTER</literal> is not
                 supported.
               </para>
-              
+
             </formalpara>
           </listitem>
-          
+
           <listitem>
             <formalpara>
-              
+
               <title>Savepoints and rollbacks</title>
-              
+
               <para>
-                Savepoints and rollbacks to savepoints are ignored as
-                in <literal>MyISAM</literal>.
+                Savepoints and rollbacks to savepoints are ignored as in
+                <literal>MyISAM</literal>.
               </para>
-              
+
             </formalpara>
           </listitem>
-          
+
           <listitem>
             <formalpara>
-              
+
               <title>Durability of commits</title>
-              
+
               <para>
-                There are no durable commits on disk. Commits are replicated,
-                but there is no guarantee that logs are flushed to
-                disk on commit.
+                There are no durable commits on disk. Commits are
+                replicated, but there is no guarantee that logs are
+                flushed to disk on commit.
               </para>
-              
+
             </formalpara>
           </listitem>
+
         </itemizedlist>
       </para>
-      
+
       <note>
         <para>
           See <xref linkend="mysql-cluster-limitations-transactions"/>,

@@ -18278,7 +18277,7 @@
           handling in <literal>NDB</literal>.
         </para>
       </note>
-      
+
     </section>
 
     <section id="mysql-cluster-limitations-performance">

@@ -18529,7 +18528,8 @@
           </listitem>
 
         </itemizedlist>
-        See also 
+
+        See also
         <xref linkend="mysql-cluster-limitations-multiple-nodes"/>.
       </para>
 


Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml	2007-05-22 04:22:01 UTC (rev 6557)
+++ trunk/refman-5.1/mysql-cluster.xml	2007-05-22 04:23:07 UTC (rev 6558)
Changed blocks: 7, Lines Added: 60, Lines Deleted: 51; 6489 bytes

@@ -515,7 +515,7 @@
     <para>
       (However, it should be noted MySQL does not currently support the
       use of multiple data nodes on a single computer in a production
-      setting. See 
+      setting. See
       <xref linkend="mysql-cluster-limitations-multiple-nodes"/>.)
     </para>
 

@@ -21689,7 +21689,7 @@
                 transaction isolation level. (<literal>InnoDB</literal>,
                 for example, supports <literal>READ COMMITTED</literal>,
                 <literal>READ UNCOMMITTED</literal>, <literal>REPEATABLE
-                  READ</literal>, and <literal>SERIALIZABLE</literal>.)
+                READ</literal>, and <literal>SERIALIZABLE</literal>.)
                 See
                 <xref linkend="mysql-cluster-backup-troubleshooting"/>,
                 for information on how this can affect backing up and

@@ -21795,9 +21795,16 @@
                             INFILE</literal> statement, the
                             <literal>NDB</literal> engine can and does
                             commit at will.
-			    <remark>What does "at will" exactly mean? Always? /SH
-			    <remark>[js] "Whenever it feels like it", I guess. ;) I'll ask
-			      the devs.</remark></remark>
+
+                            <remark>
+                              What does "at will" exactly mean? Always?
+                              /SH
+
+                              <remark>
+                                [js] "Whenever it feels like it", I
+                                guess. ;) I'll ask the devs.
+                              </remark>
+                            </remark>
                           </para>
                         </important>
 

@@ -21857,13 +21864,15 @@
               <title>Temporary errors</title>
 
               <para>
-		      <remark>
-		        We need to add visual markup (CSS etc.) for the errortext 
-		        element. /SH
-		        <remark>
-		          [js] Sent MC an email asking for help with this.
-		        </remark> 
-		      </remark>
+                <remark>
+                  We need to add visual markup (CSS etc.) for the
+                  errortext element. /SH
+
+                  <remark>
+                    [js] Sent MC an email asking for help with this.
+                  </remark>
+                </remark>
+
                 When first starting a node, it is possible that you may
                 see Error 1204 <errortext>Temporary failure,
                 distribution changed</errortext> and similar temporary

@@ -21999,93 +22008,92 @@
     </section>
 
     <section id="mysql-cluster-limitations-unsupported-missing">
-      
+
       <title>Unsupported Or Missing Features</title>
-      
+
       <indexterm>
         <primary>MySQL Cluster limitations</primary>
         <secondary>unsupported features</secondary>
       </indexterm>
-      
-      
-      
+
       <para>
-        A number of features supported by other storage engines are
-        not supported for <literal>NDB</literal> tables. Trying to use
-        any of these features in MySQL Cluster does not cause errors
-        in or of itself; however, errors may occur in applications
-        that expects the features to be supported or enforced:
-        
+        A number of features supported by other storage engines are not
+        supported for <literal>NDB</literal> tables. Trying to use any
+        of these features in MySQL Cluster does not cause errors in or
+        of itself; however, errors may occur in applications that
+        expects the features to be supported or enforced:
+
         <itemizedlist>
-          
+
           <listitem>
             <formalpara>
-              
+
               <title>Foreign key constraints</title>
-              
+
               <para>
                 The foreign key construct is ignored, just as it is in
                 <literal>MyISAM</literal> tables.
               </para>
-              
+
             </formalpara>
           </listitem>
-          
+
           <listitem>
             <formalpara>
-              
+
               <title><literal>OPTIMIZE</literal> operations</title>
-              
+
               <para>
                 <literal>OPTIMIZE</literal> operations are not
                 supported.
               </para>
-              
+
             </formalpara>
           </listitem>
-          
+
           <listitem>
             <formalpara>
-              
+
               <title><literal>LOAD TABLE ... FROM MASTER</literal></title>
-              
+
               <para>
                 <literal>LOAD TABLE ... FROM MASTER</literal> is not
                 supported.
               </para>
-              
+
             </formalpara>
           </listitem>
-          
+
           <listitem>
             <formalpara>
-              
+
               <title>Savepoints and rollbacks</title>
-              
+
               <para>
-                Savepoints and rollbacks to savepoints are ignored as
-                in <literal>MyISAM</literal>.
+                Savepoints and rollbacks to savepoints are ignored as in
+                <literal>MyISAM</literal>.
               </para>
-              
+
             </formalpara>
           </listitem>
-          
+
           <listitem>
             <formalpara>
-              
+
               <title>Durability of commits</title>
-              
+
               <para>
-                There are no durable commits on disk. Commits are replicated,
-                but there is no guarantee that logs are flushed to
-                disk on commit.
+                There are no durable commits on disk. Commits are
+                replicated, but there is no guarantee that logs are
+                flushed to disk on commit.
               </para>
-              
+
             </formalpara>
           </listitem>
+
         </itemizedlist>
       </para>
-      
+
       <note>
         <para>
           See <xref linkend="mysql-cluster-limitations-transactions"/>,

@@ -22093,7 +22101,7 @@
           handling in <literal>NDB</literal>.
         </para>
       </note>
-      
+
     </section>
 
     <section id="mysql-cluster-limitations-performance">

@@ -22329,7 +22337,8 @@
           </listitem>
 
         </itemizedlist>
-        See also 
+
+        See also
         <xref linkend="mysql-cluster-limitations-multiple-nodes"/>.
       </para>
 


Thread
svn commit - mysqldoc@docsrva: r6558 - in trunk: refman-4.1 refman-5.0 refman-5.1jon22 May