List:Commits« Previous MessageNext Message »
From:paul Date:January 8 2006 1:29am
Subject:svn commit - mysqldoc@docsrva: r717 - in trunk: . refman-4.1 refman-5.0 refman-5.1
View as plain text  
Author: paul
Date: 2006-01-08 02:29:03 +0100 (Sun, 08 Jan 2006)
New Revision: 717

Log:
 r5949@frost:  paul | 2006-01-07 19:07:24 -0600
 Add tags.


Modified:
   trunk/
   trunk/refman-4.1/connector-j.xml
   trunk/refman-4.1/database-administration.xml
   trunk/refman-4.1/innodb.xml
   trunk/refman-4.1/ndbcluster.xml
   trunk/refman-5.0/connector-j.xml
   trunk/refman-5.0/database-administration.xml
   trunk/refman-5.0/ndbcluster.xml
   trunk/refman-5.1/connector-j.xml
   trunk/refman-5.1/database-administration.xml
   trunk/refman-5.1/ndbcluster.xml
   trunk/refman-5.1/pluggable-storage.xml


Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:5948
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1994
   + b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:5949
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1994

Modified: trunk/refman-4.1/connector-j.xml
===================================================================
--- trunk/refman-4.1/connector-j.xml	2006-01-08 01:28:29 UTC (rev 716)
+++ trunk/refman-4.1/connector-j.xml	2006-01-08 01:29:03 UTC (rev 717)
@@ -2741,7 +2741,7 @@
 
           <para>
             The earliest the locks these statements hold can be released
-            (whether they be MyISAM table-level locks or row-level locks
+            (whether they be <literal>MyISAM</literal> table-level locks or row-level locks
             in some other storage engine such as InnoDB) is when the
             statement completes.
           </para>

Modified: trunk/refman-4.1/database-administration.xml
===================================================================
--- trunk/refman-4.1/database-administration.xml	2006-01-08 01:28:29 UTC (rev 716)
+++ trunk/refman-4.1/database-administration.xml	2006-01-08 01:29:03 UTC (rev 717)
@@ -9469,7 +9469,7 @@
 
         <para>
           Each storage engine performs any actions necessary for tables
-          that it manages. For example, MyISAM flushes any pending index
+          that it manages. For example, <literal>MyISAM</literal> flushes any pending index
           writes for a table. InnoDB flushes its buffer pool to disk,
           writes the current LSN to the tablespace, and terminates its
           own internal threads.

Modified: trunk/refman-4.1/innodb.xml
===================================================================
--- trunk/refman-4.1/innodb.xml	2006-01-08 01:28:29 UTC (rev 716)
+++ trunk/refman-4.1/innodb.xml	2006-01-08 01:29:03 UTC (rev 717)
@@ -1347,8 +1347,8 @@
           TABLES</literal>; MySQL does not return from <literal>LOCK
           TABLE .. WRITE</literal> until all other threads have released
           all their locks to the table. In MySQL 4.0.19 and before,
-          InnoDB ignored table locks, which allowed one to more easily
-          simulate transactions with a combination of MyISAM and InnoDB
+          <literal>InnoDB</literal> ignored table locks, which allowed one to more easily
+          simulate transactions with a combination of <literal>MyISAM</literal> and <literal>InnoDB</literal>
           tables. The default value is 1, which means that <literal>LOCK
           TABLES</literal> causes also InnoDB internally to take a table
           lock. In applications using <literal>AUTOCOMMIT=1</literal>,

Modified: trunk/refman-4.1/ndbcluster.xml
===================================================================
--- trunk/refman-4.1/ndbcluster.xml	2006-01-08 01:28:29 UTC (rev 716)
+++ trunk/refman-4.1/ndbcluster.xml	2006-01-08 01:29:03 UTC (rev 717)
@@ -8739,7 +8739,7 @@
     <para>
       In this section, we provide a listing of known limitations in
       MySQL Cluster releases in the &current-series;.x series when
-      compared to features available when using the MyISAM and InnoDB
+      compared to features available when using the <literal>MyISAM</literal> and InnoDB
       storage engines. Currently there are no plans to address these in
       coming releases of MySQL &current-series;; however, we will
       attempt to supply fixes for these issues in subsequent release

Modified: trunk/refman-5.0/connector-j.xml
===================================================================
--- trunk/refman-5.0/connector-j.xml	2006-01-08 01:28:29 UTC (rev 716)
+++ trunk/refman-5.0/connector-j.xml	2006-01-08 01:29:03 UTC (rev 717)
@@ -2741,7 +2741,7 @@
 
           <para>
             The earliest the locks these statements hold can be released
-            (whether they be MyISAM table-level locks or row-level locks
+            (whether they be <literal>MyISAM</literal> table-level locks or row-level locks
             in some other storage engine such as InnoDB) is when the
             statement completes.
           </para>

Modified: trunk/refman-5.0/database-administration.xml
===================================================================
--- trunk/refman-5.0/database-administration.xml	2006-01-08 01:28:29 UTC (rev 716)
+++ trunk/refman-5.0/database-administration.xml	2006-01-08 01:29:03 UTC (rev 717)
@@ -6190,12 +6190,14 @@
                   </row>
                   <row>
                     <entry>1</entry>
-                    <entry>(Default) Enables concurrent insert for MyISAM tables that don't have
+                    <entry>(Default) Enables concurrent insert for
+<literal>MyISAM</literal> tables that don't have
                       holes</entry>
                   </row>
                   <row>
                     <entry>2</entry>
-                    <entry>Enables concurrent inserts for all MyISAM tables. If table has a hole
+                    <entry>Enables concurrent inserts for all
+<literal>MyISAM</literal> tables. If table has a hole
                       and is in use by another thread the new row will
                       be inserted at end of table. If table is not in
                       use then MySQL will do a normal read lock and
@@ -7032,7 +7034,7 @@
             </para>
 
             <para>
-              It is possible to create multiple MyISAM key caches. The
+              It is possible to create multiple <literal>MyISAM</literal> key caches. The
               size limit of 4GB applies to each cache individually, not
               as a group. See <xref linkend="myisam-key-cache"/>.
             </para>
@@ -11428,7 +11430,7 @@
 
         <para>
           Each storage engine performs any actions necessary for tables
-          that it manages. For example, MyISAM flushes any pending index
+          that it manages. For example, <literal>MyISAM</literal> flushes any pending index
           writes for a table. InnoDB flushes its buffer pool to disk
           (starting from 5.0.5: unless
           <literal>innodb_fast_shutdown</literal> is 2), writes the

Modified: trunk/refman-5.0/ndbcluster.xml
===================================================================
--- trunk/refman-5.0/ndbcluster.xml	2006-01-08 01:28:29 UTC (rev 716)
+++ trunk/refman-5.0/ndbcluster.xml	2006-01-08 01:29:03 UTC (rev 717)
@@ -8720,7 +8720,7 @@
     <para>
       In this section, we provide a listing of known limitations in
       MySQL Cluster releases in the &current-series;.x series when
-      compared to features available when using the MyISAM and InnoDB
+      compared to features available when using the <literal>MyISAM</literal> and InnoDB
       storage engines. Currently there are no plans to address these in
       coming releases of MySQL &current-series;; however, we will
       attempt to supply fixes for these issues in subsequent release

Modified: trunk/refman-5.1/connector-j.xml
===================================================================
--- trunk/refman-5.1/connector-j.xml	2006-01-08 01:28:29 UTC (rev 716)
+++ trunk/refman-5.1/connector-j.xml	2006-01-08 01:29:03 UTC (rev 717)
@@ -2741,7 +2741,7 @@
 
           <para>
             The earliest the locks these statements hold can be released
-            (whether they be MyISAM table-level locks or row-level locks
+            (whether they be <literal>MyISAM</literal> table-level locks or row-level locks
             in some other storage engine such as InnoDB) is when the
             statement completes.
           </para>

Modified: trunk/refman-5.1/database-administration.xml
===================================================================
--- trunk/refman-5.1/database-administration.xml	2006-01-08 01:28:29 UTC (rev 716)
+++ trunk/refman-5.1/database-administration.xml	2006-01-08 01:29:03 UTC (rev 717)
@@ -6167,12 +6167,14 @@
                   </row>
                   <row>
                     <entry>1</entry>
-                    <entry>(Default) Enables concurrent insert for MyISAM tables that don't have
+                    <entry>(Default) Enables concurrent insert for
+<literal>MyISAM</literal> tables that don't have
                       holes</entry>
                   </row>
                   <row>
                     <entry>2</entry>
-                    <entry>Enables concurrent inserts for all MyISAM tables. If table has a hole
+                    <entry>Enables concurrent inserts for all
+<literal>MyISAM</literal> tables. If table has a hole
                       and is in use by another thread the new row will
                       be inserted at end of table. If table is not in
                       use then MySQL will do a normal read lock and
@@ -7023,7 +7025,7 @@
             </para>
 
             <para>
-              It is possible to create multiple MyISAM key caches. The
+              It is possible to create multiple <literal>MyISAM</literal> key caches. The
               size limit of 4GB applies to each cache individually, not
               as a group. See <xref linkend="myisam-key-cache"/>.
             </para>
@@ -11405,7 +11407,7 @@
 
         <para>
           Each storage engine performs any actions necessary for tables
-          that it manages. For example, MyISAM flushes any pending index
+          that it manages. For example, <literal>MyISAM</literal> flushes any pending index
           writes for a table. InnoDB flushes its buffer pool to disk
           unless <literal>innodb_fast_shutdown</literal> is 2), writes
           the current LSN to the tablespace, and terminates its own

Modified: trunk/refman-5.1/ndbcluster.xml
===================================================================
--- trunk/refman-5.1/ndbcluster.xml	2006-01-08 01:28:29 UTC (rev 716)
+++ trunk/refman-5.1/ndbcluster.xml	2006-01-08 01:29:03 UTC (rev 717)
@@ -10332,7 +10332,7 @@
     <para>
       In this section, we provide a listing of known limitations in
       MySQL Cluster releases in the &current-series;.x series when
-      compared to features available when using the MyISAM and InnoDB
+      compared to features available when using the <literal>MyISAM</literal> and InnoDB
       storage engines. Currently there are no plans to address these in
       coming releases of MySQL &current-series;; however, we will
       attempt to supply fixes for these issues in subsequent release

Modified: trunk/refman-5.1/pluggable-storage.xml
===================================================================
--- trunk/refman-5.1/pluggable-storage.xml	2006-01-08 01:28:29 UTC (rev 716)
+++ trunk/refman-5.1/pluggable-storage.xml	2006-01-08 01:29:03 UTC (rev 717)
@@ -286,7 +286,8 @@
       <listitem>
         <para>
           <literal>Merge</literal> - allows a MySQL DBA or developer to
-          logically group together a series of identical MyISAM tables
+          logically group together a series of identical
+<literal>MyISAM</literal> tables
           and reference them as one object. Good for VLDB environments
           like data warehousing.
         </para>

Thread
svn commit - mysqldoc@docsrva: r717 - in trunk: . refman-4.1 refman-5.0 refman-5.1paul8 Jan