List:Commits« Previous MessageNext Message »
From:john.russell Date:April 7 2011 7:39pm
Subject:svn commit - mysqldoc@oter02: r25789 - trunk/refman-5.6
View as plain text  
Author: jdrussel
Date: 2011-04-07 21:39:04 +0200 (Thu, 07 Apr 2011)
New Revision: 25789

Log:
Fix missing ID that only shows up when generating the dyn* file, not in validating the *core* file.
Not clear to me how <literal role="stmt"> interacts with statements like SHOW ENGINE INNODB STATUS
that have so many parts and variations. Put the <literal> tag only around part of the phrase,
or some other syntax for the <literal> attributes to specify where to auto-link?


Modified:
   trunk/refman-5.6/se-innodb-core.xml


Modified: trunk/refman-5.6/se-innodb-core.xml
===================================================================
--- trunk/refman-5.6/se-innodb-core.xml	2011-04-07 19:22:21 UTC (rev 25788)
+++ trunk/refman-5.6/se-innodb-core.xml	2011-04-07 19:39:04 UTC (rev 25789)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 1121 bytes

@@ -11713,9 +11713,9 @@
             <literal>InnoDB</literal> user transactions is recorded in
             the <literal>mysqld</literal> error log. Otherwise, you see
             information about only the last deadlock, using the
-            <literal role="stmt">SHOW ENGINE INNODB STATUS</literal>
-            command. An occasional <literal>InnoDB</literal> deadlock is
-            not necessarily an issue, because <literal>InnoDB</literal>
+            <literal>SHOW ENGINE INNODB STATUS</literal> command. An
+            occasional <literal>InnoDB</literal> deadlock is not
+            necessarily an issue, because <literal>InnoDB</literal>
             detects the condition immediately, and rolls back one of the
             transactions automatically. You might use this option to
             troubleshoot why deadlocks are happening if an application


Thread
svn commit - mysqldoc@oter02: r25789 - trunk/refman-5.6john.russell7 Apr