List:Commits« Previous MessageNext Message »
From:john.russell Date:March 26 2011 12:32am
Subject:svn commit - mysqldoc@oter02: r25567 - trunk/innodb-1.1
View as plain text  
Author: jdrussel
Date: 2011-03-26 01:32:17 +0100 (Sat, 26 Mar 2011)
New Revision: 25567

Log:
Couple of little validation glitches.


Modified:
   trunk/innodb-1.1/innodb-information-schema.xml
   trunk/innodb-1.1/innodb-row-format.xml


Modified: trunk/innodb-1.1/innodb-information-schema.xml
===================================================================
--- trunk/innodb-1.1/innodb-information-schema.xml	2011-03-26 00:31:04 UTC (rev 25566)
+++ trunk/innodb-1.1/innodb-information-schema.xml	2011-03-26 00:32:17 UTC (rev 25567)
Changed blocks: 5, Lines Added: 9, Lines Deleted: 5; 2320 bytes

@@ -1489,7 +1489,8 @@
 
   <section id="innodb-information-schema-notes">
 
-    <title>Notes on Locking in InnoDB</title>
+    <title>Special Locking Considerations for InnoDB
+      <literal>INFORMATION_SCHEMA</literal> Tables</title>
 
     <indexterm>
       <primary>Locking</primary>

@@ -1502,6 +1503,9 @@
 
 <!-- JDR: doesn't seem related to the 2 sections that follow it -->
 
+<!-- JDR: if the info is all contained in the main SE::InnoDB section, remove this first subheading
+and just cross-reference to the locking background info. -->
+
       <title>Understanding InnoDB Locking</title>
 
       <para>

@@ -1515,7 +1519,7 @@
         corresponding queue. For a lock to be acquired by a transaction,
         all incompatible lock requests previously entered into the lock
         queue for that row or table must be removed (the transactions
-        holding or requesting those locks either commit or rollback).
+        holding or requesting those locks either commit or roll back).
       </para>
 
       <para>

@@ -1532,13 +1536,13 @@
 
       <para>
         The table
-        <link linkend='innodb-information-schema-innodb_locks'><literal>INNODB_LOCKS</literal></link>
+        <link linkend="innodb-information-schema-innodb_locks"><literal>INNODB_LOCKS</literal></link>
         holds one or more row for each <literal>'LOCK WAIT'</literal>
         transaction, indicating the lock request(s) that is (are)
         preventing its progress. This table also contains one row
         describing each lock in a queue of locks pending for a given row
         or table. The table
-        <link linkend='innodb-information-schema-innodb_lock_waits'><literal>INNODB_LOCK_WAITS</literal></link>
+        <link linkend="innodb-information-schema-innodb_lock_waits"><literal>INNODB_LOCK_WAITS</literal></link>
         shows which locks already held by a transaction are blocking
         locks requested by other transactions.
       </para>

@@ -1647,4 +1651,4 @@
   </section>
 
 </chapter>
-<!-- vim: set sw=2 tw=72: -->
+<!-- vim: set sw=2 tw=100: -->


Modified: trunk/innodb-1.1/innodb-row-format.xml
===================================================================
--- trunk/innodb-1.1/innodb-row-format.xml	2011-03-26 00:31:04 UTC (rev 25566)
+++ trunk/innodb-1.1/innodb-row-format.xml	2011-03-26 00:32:17 UTC (rev 25567)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 803 bytes

@@ -59,7 +59,7 @@
       that are too long to fit on a B-tree page are stored on separately
       allocated disk pages called
       <link linkend="glos_overflow_page">overflow pages</link>. We call
-      such columns <link linkend="glos_off_page_columns">off-page
+      such columns <link linkend="glos_off_page_column">off-page
       column</link>. The values of these columns are stored on
       singly-linked lists of overflow pages, and each such column has
       its own list of one or more overflow pages. In some cases, all or


Thread
svn commit - mysqldoc@oter02: r25567 - trunk/innodb-1.1john.russell26 Mar