List:Commits« Previous MessageNext Message »
From:jon Date:October 7 2006 6:42am
Subject:svn commit - mysqldoc@docsrva: r3572 - in trunk: refman-5.0 refman-5.1
View as plain text  
Author: jstephens
Date: 2006-10-07 08:42:07 +0200 (Sat, 07 Oct 2006)
New Revision: 3572

Log:

Misc. typo/wording/markup fixes in new-5.0/news-5.1

Reformat



Modified:
   trunk/refman-5.0/news-5.0.xml
   trunk/refman-5.0/se-innodb.xml
   trunk/refman-5.0/sql-syntax.xml
   trunk/refman-5.1/news-5.1.xml
   trunk/refman-5.1/se-innodb.xml
   trunk/refman-5.1/sql-syntax.xml


Modified: trunk/refman-5.0/news-5.0.xml
===================================================================
--- trunk/refman-5.0/news-5.0.xml	2006-10-07 06:34:27 UTC (rev 3571)
+++ trunk/refman-5.0/news-5.0.xml	2006-10-07 06:42:07 UTC (rev 3572)
Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 1129 bytes

@@ -322,7 +322,7 @@
           alternatives. (Bug #18822)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>LOAD DATA INFILE</literal> no longer causes an

@@ -16075,7 +16075,7 @@
       <listitem>
         <para>
           If, on a replication master a <literal>LOAD DATA
-            INFILE</literal> operation was interrupted (by, for example,
+          INFILE</literal> operation was interrupted (by, for example,
           an integrity constraint violation or killed connection), the
           slave skipped the <literal>LOAD DATA INFILE</literal>
           entirely, thus missing changes if this command permanently

@@ -19024,7 +19024,7 @@
           changed compared to that of MySQL 4.1 and older.
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>LOAD DATA INFILE</literal> causes an implicit commit.


Modified: trunk/refman-5.0/se-innodb.xml
===================================================================
--- trunk/refman-5.0/se-innodb.xml	2006-10-07 06:34:27 UTC (rev 3571)
+++ trunk/refman-5.0/se-innodb.xml	2006-10-07 06:42:07 UTC (rev 3572)
Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 1207 bytes

@@ -1247,6 +1247,7 @@
           disable the caching of disk writes in hardware caches, or use
           some other command specific to the hardware vendor.
         </para>
+
         <para>
           Note: For the greatest possible durability and consistency in
           a replication setup using <literal>InnoDB</literal> with

@@ -1326,7 +1327,6 @@
           the <literal>LOCK TABLES</literal> statement. The default is
           50 seconds.
         </para>
-
       </listitem>
 
       <listitem>

@@ -4528,12 +4528,12 @@
             statements the user made during that transaction.
           </para>
         </listitem>
-        
+
         <listitem>
           <para>
             Prior to MySQL 5.0.26, <literal>LOAD DATA INFILE</literal>
             also caused an implicit commit for <literal>InnoDB</literal>
-            tables (as was true for all storage engines). 
+            tables (as was true for all storage engines).
           </para>
         </listitem>
 


Modified: trunk/refman-5.0/sql-syntax.xml
===================================================================
--- trunk/refman-5.0/sql-syntax.xml	2006-10-07 06:34:27 UTC (rev 3571)
+++ trunk/refman-5.0/sql-syntax.xml	2006-10-07 06:42:07 UTC (rev 3572)
Changed blocks: 3, Lines Added: 7, Lines Deleted: 7; 1795 bytes

@@ -10959,14 +10959,14 @@
             statements the user made during that transaction.
           </para>
         </listitem>
-        
+
         <listitem>
           <para>
             In MySQL 5.0.25 and earlier, <literal>LOAD DATA
-              INFILE</literal> caused an implicit commit for all storage
+            INFILE</literal> caused an implicit commit for all storage
             engines. Beginning with MySQL 5.0.26, it causes an implicit
-            commit only for tables using the <literal>NDB</literal> storage
-            engine. For more information, see Bug #11151.
+            commit only for tables using the <literal>NDB</literal>
+            storage engine. For more information, see Bug #11151.
           </para>
         </listitem>
 

@@ -16504,7 +16504,7 @@
 Support: YES
 Comment: /dev/null storage engine (anything you write to it disappears)
 </programlisting>
-        
+
         <para>
           The output from <literal>SHOW ENGINES</literal> may vary
           according to the MySQL version used and other factors. The

@@ -19440,8 +19440,8 @@
               (<emphasis>DEPRECATED</emphasis>). Deletes all binary
               logs, resets the binary log index file and creates a new
               binary log. Deprecated in favor of <literal>RESET
-              MASTER</literal>, supported for backwards compatibility only
-              See <xref
+              MASTER</literal>, supported for backwards compatibility
+              only See <xref
               linkend="reset-master"/>.
             </para>
           </listitem>


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2006-10-07 06:34:27 UTC (rev 3571)
+++ trunk/refman-5.1/news-5.1.xml	2006-10-07 06:42:07 UTC (rev 3572)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 457 bytes

@@ -678,7 +678,7 @@
           <xref linkend="udf-compiling"/>. (Bug #19121)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>LOAD DATA INFILE</literal> no longer causes an


Modified: trunk/refman-5.1/se-innodb.xml
===================================================================
--- trunk/refman-5.1/se-innodb.xml	2006-10-07 06:34:27 UTC (rev 3571)
+++ trunk/refman-5.1/se-innodb.xml	2006-10-07 06:42:07 UTC (rev 3572)
Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 1207 bytes

@@ -1243,6 +1243,7 @@
           disable the caching of disk writes in hardware caches, or use
           some other command specific to the hardware vendor.
         </para>
+
         <para>
           Note: For the greatest possible durability and consistency in
           a replication setup using <literal>InnoDB</literal> with

@@ -1319,7 +1320,6 @@
           the <literal>LOCK TABLES</literal> statement. The default is
           50 seconds.
         </para>
-
       </listitem>
 
       <listitem>

@@ -4491,12 +4491,12 @@
             statements the user made during that transaction.
           </para>
         </listitem>
-        
+
         <listitem>
           <para>
             Prior to MySQL 5.1.12, <literal>LOAD DATA INFILE</literal>
             also caused an implicit commit for <literal>InnoDB</literal>
-            tables (as was true for all storage engines). 
+            tables (as was true for all storage engines).
           </para>
         </listitem>
 


Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml	2006-10-07 06:34:27 UTC (rev 3571)
+++ trunk/refman-5.1/sql-syntax.xml	2006-10-07 06:42:07 UTC (rev 3572)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 4; 1002 bytes

@@ -12297,14 +12297,14 @@
             statements the user made during that transaction.
           </para>
         </listitem>
-        
+
         <listitem>
           <para>
             In MySQL 5.1.11 and earlier, <literal>LOAD DATA
-              INFILE</literal> caused an implicit commit for all storage
+            INFILE</literal> caused an implicit commit for all storage
             engines. Beginning with MySQL 5.1.12, it causes an implicit
-            commit only for tables using the <literal>NDB</literal> storage
-            engine. For more information, see Bug #11151.
+            commit only for tables using the <literal>NDB</literal>
+            storage engine. For more information, see Bug #11151.
           </para>
         </listitem>
 


Thread
svn commit - mysqldoc@docsrva: r3572 - in trunk: refman-5.0 refman-5.1jon7 Oct