List:Commits« Previous MessageNext Message »
From:jon.stephens Date:April 27 2011 12:17pm
Subject:svn commit - mysqldoc@oter02: r26031 - in trunk: dynamic-docs/changelog ndbapi refman-5.1
View as plain text  
Author: js221926
Date: 2011-04-27 14:17:30 +0200 (Wed, 27 Apr 2011)
New Revision: 26031

Log:

Add auto-link markup for ndbinfo database/tables (BUG#12402219)

Fix section ID (contained underscore), add IDs to renamed-nodes.txt

Remove some now-redundant xrefs





Modified:
   trunk/dynamic-docs/changelog/mysqld-2.xml
   trunk/ndbapi/ndb-internals.xml
   trunk/refman-5.1/mysql-cluster-configuration-core.xml
   trunk/refman-5.1/mysql-cluster-management.xml
   trunk/refman-5.1/mysql-cluster-multi-computer.xml
   trunk/refman-5.1/mysql-cluster-overview.xml
   trunk/refman-5.1/renamed-nodes.txt


Modified: trunk/dynamic-docs/changelog/mysqld-2.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-2.xml	2011-04-27 09:45:12 UTC (rev 26030)
+++ trunk/dynamic-docs/changelog/mysqld-2.xml	2011-04-27 12:17:30 UTC (rev 26031)
Changed blocks: 12, Lines Added: 51, Lines Deleted: 49; 8406 bytes

@@ -173,12 +173,12 @@
 
       <para>
         A <literal>config_generation</literal> column has been added to
-        the <literal>ndbinfo.nodes</literal> table. By checking this
-        column, it is now possible to determine which version or
-        versions of the MySQL Cluster configuration file are in effect
-        on the data nodes. This information can be especially useful
-        when performing a rolling restart of the cluster in order to
-        update its configuration. For more information, see
+        the <literal role="ndbinfo">ndbinfo.nodes</literal> table. By
+        checking this column, it is now possible to determine which
+        version or versions of the MySQL Cluster configuration file are
+        in effect on the data nodes. This information can be especially
+        useful when performing a rolling restart of the cluster in order
+        to update its configuration. For more information, see
         <xref linkend="mysql-cluster-ndbinfo-nodes"/>.
       </para>
 

@@ -232,9 +232,10 @@
         given join is pushed down using
         <literal role="stmt">EXPLAIN</literal>. In addition, several new
         counters relating to push-down join performance have been added
-        to the <literal>ndbinfo.counters</literal> table. For more
-        information, see the descriptions of these status variables, as
-        well as <xref linkend="mysql-cluster-ndbinfo-counters"/>.
+        to the <literal role="ndbinfo">ndbinfo.counters</literal> table.
+        For more information, see the descriptions of these status
+        variables, as well as
+        <xref linkend="mysql-cluster-ndbinfo-counters"/>.
       </para>
 
     </message>

@@ -2365,11 +2366,12 @@
     <message>
 
       <para>
-        Successive queries on the <literal>ndbinfo.counters</literal>
-        table from the same SQL node returned unchanging results. To fix
-        this issue, and to prevent similar issues from occurring in the
-        future, <literal>ndbinfo</literal> tables are now excluded from
-        the query cache.
+        Successive queries on the
+        <literal role="ndbinfo">ndbinfo.counters</literal> table from
+        the same SQL node returned unchanging results. To fix this
+        issue, and to prevent similar issues from occurring in the
+        future, <literal role="ndbinfo">ndbinfo</literal> tables are now
+        excluded from the query cache.
       </para>
 
     </message>

@@ -5171,10 +5173,10 @@
       <para>
         A new <literal>diskpagebuffer</literal> table, providing
         statistics on disk page buffer usage by Disk Data tables, is
-        added to the <literal>ndbinfo</literal> information database.
-        These statistics can be used to monitor performance of reads and
-        writes on Disk Data tables, and to assist in the tuning of
-        related parameters such as
+        added to the <literal role="ndbinfo">ndbinfo</literal>
+        information database. These statistics can be used to monitor
+        performance of reads and writes on Disk Data tables, and to
+        assist in the tuning of related parameters such as
         <literal role="ndbparam:ndbd">DiskPageBufferMemory</literal>.
         For more information, see
         <xref linkend="mysql-cluster-ndbinfo-diskpagebuffer"/>.

@@ -8873,7 +8875,7 @@
 
       <para>
         It is no longer possible to make a dump of the
-        <literal>ndbinfo</literal> database using
+        <literal role="ndbinfo">ndbinfo</literal> database using
         <command>mysqldump</command>.
       </para>
 

@@ -13359,8 +13361,8 @@
 
       <para>
         The schema for the <literal>memoryusage</literal> table of the
-        <literal>ndbinfo</literal> information database has changed, as
-        detailed in the following list:
+        <literal role="ndbinfo">ndbinfo</literal> information database
+        has changed, as detailed in the following list:
       </para>
 
       <itemizedlist>

@@ -15063,12 +15065,11 @@
     <message>
 
       <para>
-        The experimental <literal>ndbinfo.pools</literal> table has been
-        removed. Information useful to MySQL Cluster administration that
-        was contained in this table should be available from other
-        <literal>ndbinfo</literal> tables. See
-        <xref linkend="mysql-cluster-ndbinfo"/>, for additional
-        information.
+        The experimental <literal role="ndbinfo">ndbinfo.pools</literal>
+        table has been removed. Information useful to MySQL Cluster
+        administration that was contained in this table should be
+        available from other <literal role="ndbinfo">ndbinfo</literal>
+        tables.
       </para>
 
     </message>

@@ -15700,8 +15701,8 @@
 
       <para>
         A <command>mysqld</command>, when attempting to access the
-        <literal>ndbinfo</literal> database, crashed if could not
-        contact the management server.
+        <literal role="ndbinfo">ndbinfo</literal> database, crashed if
+        could not contact the management server.
       </para>
 
     </message>

@@ -15900,8 +15901,9 @@
     <message>
 
       <para>
-        Some values shown in the <literal>ndbinfo.memoryusage</literal>
-        table did not match corresponding values shown by the
+        Some values shown in the
+        <literal role="ndbinfo">ndbinfo.memoryusage</literal> table did
+        not match corresponding values shown by the
         <command>ndb_mgm</command> client <literal>ALL REPORT
         MEMORYUSAGE</literal> command.
       </para>

@@ -17724,8 +17726,8 @@
 
       <para>
         The <literal>DATA_MEMORY</literal> column of the
-        <literal>ndbinfo.memoryusage</literal> table was renamed to
-        <literal>memory_type</literal>.
+        <literal role="ndbinfo">ndbinfo.memoryusage</literal> table was
+        renamed to <literal>memory_type</literal>.
       </para>
 
     </message>

@@ -17752,9 +17754,8 @@
     <message>
 
       <para>
-        The <literal>ndbinfo.transporters</literal> table (see
-        <xref linkend="mysql-cluster-ndbinfo-transporters"/>) showed the
-        status of a disconnected node as
+        The <literal role="ndbinfo">ndbinfo.transporters</literal> table
+        showed the status of a disconnected node as
         <literal>DISCONNECTING</literal> rather than
         <literal>DISCONNECTED</literal>.
       </para>

@@ -18448,22 +18449,23 @@
     <message>
 
       <para>
-        The <literal>ndbinfo</literal> database is added to provide
-        MySQL Cluster metadata in real time. The tables making up this
-        database contain information about memory, buffer, and other
-        resource usage, as well as configuration paramaters and
-        settings, event counts, and other useful data. Access to
-        <literal>ndbinfo</literal> is done by executing standard SQL
-        queries on its tables using the <command>mysql</command>
-        command-line client or other MySQL client application. No
-        special setup procedures are required;
-        <literal>ndbinfo</literal> is created automatically and visible
-        in the output of <literal role="stmt">SHOW DATABASES</literal>
-        when the MySQL Server is connected to a MySQL Cluster.
+        The <literal role="ndbinfo">ndbinfo</literal> database is added
+        to provide MySQL Cluster metadata in real time. The tables
+        making up this database contain information about memory,
+        buffer, and other resource usage, as well as configuration
+        paramaters and settings, event counts, and other useful data.
+        Access to <literal role="ndbinfo">ndbinfo</literal> is done by
+        executing standard SQL queries on its tables using the
+        <command>mysql</command> command-line client or other MySQL
+        client application. No special setup procedures are required;
+        <literal role="ndbinfo">ndbinfo</literal> is created
+        automatically and visible in the output of
+        <literal role="stmt">SHOW DATABASES</literal> when the MySQL
+        Server is connected to a MySQL Cluster.
       </para>
 
       <para>
-        For more information about <literal>ndbinfo</literal>, see
+        For more information, see
         <xref linkend="mysql-cluster-ndbinfo"/>.
       </para>
 


Modified: trunk/ndbapi/ndb-internals.xml
===================================================================
--- trunk/ndbapi/ndb-internals.xml	2011-04-27 09:45:12 UTC (rev 26030)
+++ trunk/ndbapi/ndb-internals.xml	2011-04-27 12:17:30 UTC (rev 26031)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 729 bytes

@@ -2258,8 +2258,8 @@
             information (see
             <xref linkend="mysql-cluster-mgm-client-commands"/>).
             Beginning with MySQL Cluster NDB 7.1.0, you can also query
-            the <literal>ndbinfo</literal> database for this information
-            (see <xref linkend="mysql-cluster-ndbinfo-memoryusage"/>).
+            the <literal role="ndbinfo">ndbinfo.memoryusage</literal>
+            table for this information.
           </para>
 
         </formalpara>


Modified: trunk/refman-5.1/mysql-cluster-configuration-core.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-configuration-core.xml	2011-04-27 09:45:12 UTC (rev 26030)
+++ trunk/refman-5.1/mysql-cluster-configuration-core.xml	2011-04-27 12:17:30 UTC (rev 26031)
Changed blocks: 6, Lines Added: 19, Lines Deleted: 19; 4058 bytes

@@ -4557,18 +4557,17 @@
 
           <para>
             When a data node is configured with
-            <literal role="ndbparam:ndbd">Nodegroup = 65536</literal>, is
-            regarded as not being assigned to any node group. When that
-            is done, the cluster waits
+            <literal role="ndbparam:ndbd">Nodegroup = 65536</literal>,
+            is regarded as not being assigned to any node group. When
+            that is done, the cluster waits
             <literal>StartNoNodegroupTimeout</literal> milliseconds,
             then treats such nodes as though they had been added to the
             list passed to the
             <option role="ndbd">--nowait-nodes</option> option, and
-            starts. The default value is <literal>15000</literal> (that is, the
-            management server waits 15
-            seconds). Setting this parameter equal to
-            <literal>0</literal> means that the cluster waits
-            indefinitely.
+            starts. The default value is <literal>15000</literal> (that
+            is, the management server waits 15 seconds). Setting this
+            parameter equal to <literal>0</literal> means that the
+            cluster waits indefinitely.
           </para>
 
           <para>

@@ -6654,9 +6653,9 @@
 
           <para>
             Beginning with MySQL Cluster NDB 7.1.9, you can query the
-            <literal>ndbinfo.diskpagebuffer</literal> table to help
-            determine whether the value for this parameter should be
-            increased to minimize unnecessary disk seeks. See
+            <literal role="ndbinfo">ndbinfo.diskpagebuffer</literal>
+            table to help determine whether the value for this parameter
+            should be increased to minimize unnecessary disk seeks. See
             <xref linkend="mysql-cluster-ndbinfo-diskpagebuffer"/>, for
             more information.
           </para>

@@ -11016,8 +11015,9 @@
 
             <listitem>
               <para>
-                The counters in the <literal>ndbinfo.counters</literal>
-                table that belong to the <literal>DBSPJ</literal> kernel
+                The counters in the
+                <literal role="ndbinfo">ndbinfo.counters</literal> table
+                that belong to the <literal>DBSPJ</literal> kernel
                 block. (These counters and the <literal>DBSPJ</literal>
                 block were also introduced in MySQL Cluster NDB 7.2.0).
                 See <xref linkend="mysql-cluster-ndbinfo-counters"/>,

@@ -11452,9 +11452,8 @@
 
       <para>
         The system variables in the following list all relate to the
-        <literal>ndbinfo</literal> information database (see
-        <xref linkend="mysql-cluster-ndbinfo"/>). They were added in
-        MySQL Cluster NDB 7.1.1.
+        <literal role="ndbinfo">ndbinfo</literal> information database.
+        They were added in MySQL Cluster NDB 7.1.1.
       </para>
 
       <itemizedlist>

@@ -11511,7 +11510,7 @@
           <para condition="dynamic:optvar:item" role="5.1:mysqld:ndbinfo_show_hidden"/>
 
           <para>
-            Whether or not the <literal>ndbinfo</literal>
+            Whether or not the <literal role="ndbinfo">ndbinfo</literal>
             database&apos;s underlying internal tables are shown in the
             <literal>mysql</literal> client. The default is
             <literal>OFF</literal>.

@@ -11546,8 +11545,9 @@
           <para condition="dynamic:optvar:item" role="5.1:mysqld:ndbinfo_version"/>
 
           <para>
-            Shows the version of the <literal>ndbinfo</literal> engine
-            in use; read-only.
+            Shows the version of the
+            <literal role="ndbinfo">ndbinfo</literal> engine in use;
+            read-only.
           </para>
         </listitem>
 


Modified: trunk/refman-5.1/mysql-cluster-management.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-management.xml	2011-04-27 09:45:12 UTC (rev 26030)
+++ trunk/refman-5.1/mysql-cluster-management.xml	2011-04-27 12:17:30 UTC (rev 26031)
Changed blocks: 10, Lines Added: 19, Lines Deleted: 22; 4978 bytes

@@ -63,8 +63,9 @@
   <para>
     In MySQL Cluster NDB 7.1.1 and later, detailed information about
     cluster operations is available in real time through an SQL
-    interface using the <literal>ndbinfo</literal> database. For more
-    information, see <xref linkend="mysql-cluster-ndbinfo"/>.
+    interface using the <literal role="ndbinfo">ndbinfo</literal>
+    database. For more information, see
+    <xref linkend="mysql-cluster-ndbinfo"/>.
   </para>
 
   <remark role="todo">

@@ -80,8 +81,7 @@
     <literal role="ndbparam:ndbd">DataMemory</literal> usage. This
     information is made available to &merlin; 2.3 or later by any MySQL
     Server which is connected to the MySQL Cluster, using
-    <literal>ndbinfo</literal> (see
-    <xref linkend="mysql-cluster-ndbinfo"/>). The advisor could be run
+    <literal role="ndbinfo">ndbinfo</literal>. The advisor could be run
     against a single MySQL Server in the Cluster, or against a pair in
     order to provide a higher level of availability for the monitoring
     service. For more information, see the

@@ -131,8 +131,7 @@
       <xref linkend="mysql-cluster-mgm-client-commands"/>). In MySQL
       Cluster NDB 7.1.1 and later, these start phases are also reported
       in the <literal>start_phase</literal> column of the
-      <literal>ndbinfo.nodes</literal> table (see
-      <xref linkend="mysql-cluster-ndbinfo-nodes"/>).
+      <literal role="ndbinfo">ndbinfo.nodes</literal> table.
     </para>
 
     <formalpara>

@@ -867,8 +866,8 @@
             <para>
               In MySQL Cluster NDB 7.1.1 and later, this information is
               also available from the
-              <literal>ndbinfo.memoryusage</literal> table; see
-              <xref linkend="mysql-cluster-ndbinfo-memoryusage"/>.
+              <literal role="ndbinfo">ndbinfo.memoryusage</literal>
+              table.
             </para>
           </listitem>
 

@@ -7910,7 +7909,7 @@
       <command>ndb_mgm</command> client to see when the cluster has
       entered single user mode. Beginning with MySQL Cluster NDB 7.1.1,
       you can also check the <literal>status</literal> column of the
-      <literal>ndbinfo.nodes</literal> table (see
+      <literal role="ndbinfo">ndbinfo.nodes</literal> table (see
       <xref linkend="mysql-cluster-ndbinfo-nodes"/>, for more
       information).
     </para>

@@ -8332,9 +8331,9 @@
 
     <para>
       Beginning with MySQL Cluster NDB 7.1.1, you can also query the
-      tables in the <literal>ndbinfo</literal> information database for
-      real-time data about many MySQL Cluster operations. See
-      <xref linkend="mysql-cluster-ndbinfo"/>.
+      tables in the <literal role="ndbinfo">ndbinfo</literal>
+      information database for real-time data about many MySQL Cluster
+      operations. See <xref linkend="mysql-cluster-ndbinfo"/>.
     </para>
 
   </section>

@@ -8630,9 +8629,10 @@
         The <literal>blocks</literal> table is a static table which
         simply contains the names and internal IDs of all NDB kernel
         blocks (see <xref linkend="ndb-internals-kernel-blocks"/>). It
-        is for use by the other <literal>ndbinfo</literal> tables (most
-        of which are actually views) in mapping block numbers to block
-        names for producing human-readable output.
+        is for use by the other
+        <literal role="ndbinfo">ndbinfo</literal> tables (most of which
+        are actually views) in mapping block numbers to block names for
+        producing human-readable output.
       </para>
 
       <para>

@@ -8676,7 +8676,7 @@
 
     </section>
 
-    <section id="mysql-cluster-ndbinfo-config_params">
+    <section id="mysql-cluster-ndbinfo-config-params">
 
       <title>The <literal>ndbinfo config_params</literal> Table</title>
 

@@ -10014,9 +10014,7 @@
         <literal>node_id</literal> is that of a data nodes which is not
         currently connected are not shown in this table. (This is
         similar omission of disconnected nodes in the
-        <literal>ndbinfo.nodes</literal> table&mdash;see
-        <xref linkend="mysql-cluster-ndbinfo-nodes"/>, for more
-        information).
+        <literal role="ndbinfo">ndbinfo.nodes</literal> table.
       </para>
 
       <para>

@@ -12994,9 +12992,8 @@
         Beginning with MySQL Cluster NDB 7.0.24 and MySQL Cluster NDB
         7.1.13, you can verify that all existing data nodes were
         restarted using the updated configuration by checking the
-        <literal>ndbinfo.nodes</literal> table in the
-        <command>mysql</command> client. (See
-        <xref linkend="mysql-cluster-ndbinfo-nodes"/>.)
+        <literal role="ndbinfo">ndbinfo.nodes</literal> table in the
+        <command>mysql</command> client.
       </para>
 
       <formalpara>


Modified: trunk/refman-5.1/mysql-cluster-multi-computer.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-multi-computer.xml	2011-04-27 09:45:12 UTC (rev 26030)
+++ trunk/refman-5.1/mysql-cluster-multi-computer.xml	2011-04-27 12:17:30 UTC (rev 26031)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 925 bytes

@@ -3274,9 +3274,9 @@
           When performing a rolling restart to update the cluster&apos;s
           configuration, you can use the
           <literal>config_generation</literal> column of the
-          <literal>ndbinfo.nodes</literal> table to keep track of which
-          data nodes have been successfully restarted with the new
-          configuration. See
+          <literal role="ndbinfo">ndbinfo.nodes</literal> table to keep
+          track of which data nodes have been successfully restarted
+          with the new configuration. See
           <xref linkend="mysql-cluster-ndbinfo-nodes"/>.
         </para>
 


Modified: trunk/refman-5.1/mysql-cluster-overview.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-overview.xml	2011-04-27 09:45:12 UTC (rev 26030)
+++ trunk/refman-5.1/mysql-cluster-overview.xml	2011-04-27 12:17:30 UTC (rev 26031)
Changed blocks: 10, Lines Added: 18, Lines Deleted: 18; 6936 bytes

@@ -485,7 +485,7 @@
       information on MySQL Cluster resources, and rules for alerts on
       key information from data nodes. (This information is made
       available to &merlin; 2.3 or later by any MySQL Server which is
-      connected to the MySQL Cluster, using <literal>ndbinfo</literal>;
+      connected to the MySQL Cluster, using <literal role="ndbinfo">ndbinfo</literal>;
       see <xref linkend="mysql-cluster-ndbinfo"/>, for more
       information). The advisor can be run against a single MySQL Server
       in the cluster or, to provide a higher level of availability for

@@ -1104,7 +1104,7 @@
               platforms.</entry>
           </row>
           <row>
-            <entry><literal>ndbinfo</literal> meta-information database</entry>
+            <entry><literal role="ndbinfo">ndbinfo</literal> meta-information database</entry>
           </row>
           <row>
             <entry>MySQL Cluster Connector for Java, including ClusterJ and OpenJPA

@@ -1398,7 +1398,7 @@
             <literal role="statvar">Ndb_pushed_queries_dropped</literal>,
             <literal role="statvar">Ndb_pushed_queries_executed</literal>,
             and <literal role="statvar">Ndb_pushed_reads</literal>) and
-            additions to the <literal>ndbinfo.counters</literal> table
+            additions to the <literal role="ndbinfo">ndbinfo.counters</literal> table
             can also be helpful in determining when and how well joins
             are being pushed down.
           </para>

@@ -1499,14 +1499,14 @@
         <listitem>
           <formalpara>
 
-            <title>MySQL Cluster information database (<literal>ndbinfo</literal>)</title>
+            <title>MySQL Cluster information database (<literal role="ndbinfo">ndbinfo</literal>)</title>
 
             <para>
-              The <literal>ndbinfo</literal> information database makes
+              The <literal role="ndbinfo">ndbinfo</literal> information database makes
               it possible to obtain real-time characteristics of a MySQL
               Cluster by issuing queries from the
               <command>mysql</command> client or other MySQL client
-              applications. <literal>ndbinfo</literal> provides metadata
+              applications. <literal role="ndbinfo">ndbinfo</literal> provides metadata
               specific to MySQL Cluster similarly to how the
               <literal>INFORMATION_SCHEMA</literal> database provides
               metadata for the standard MySQL Server. This eliminates

@@ -1527,7 +1527,7 @@
 
 <!--
           <para>
-            The addition of <literal>ndbinfo</literal> also helps
+            The addition of <literal role="ndbinfo">ndbinfo</literal> also helps
             provide support for MySQL Cluster in &merlin; 2.3 and later;
             see <xref linkend="mysql-monitor-2-3"/>.
           </para>

@@ -1790,14 +1790,14 @@
         <listitem>
           <formalpara>
 
-            <title>Change in <literal>ndbinfo</literal> database</title>
+            <title>Change in <literal role="ndbinfo">ndbinfo</literal> database</title>
 
             <para>
-              The experimental <literal>ndbinfo.pools</literal> table
-              was removed from <literal>ndbinfo</literal> in MySQL
+              The experimental <literal role="ndbinfo">ndbinfo.pools</literal> table
+              was removed from <literal role="ndbinfo">ndbinfo</literal> in MySQL
               Cluster NDB 7.1.3. Applications which used this table can
               and should be rewritten to use other
-              <literal>ndbinfo</literal> tables. For more information,
+              <literal role="ndbinfo">ndbinfo</literal> tables. For more information,
               see <xref linkend="mysql-cluster-ndbinfo-pools"/>.
             </para>
 

@@ -2023,7 +2023,7 @@
 
             <para>
               MySQL Cluster 7.1.9 introduces a new table in the
-              <literal>ndbinfo</literal> information database. The
+              <literal role="ndbinfo">ndbinfo</literal> information database. The
               <literal>diskpagebuffer</literal> table provides real-time
               data on disk page buffer usage. These statistics can be
               used to monitor performance of MySQL Cluster Disk Data

@@ -2275,13 +2275,13 @@
         <listitem>
           <formalpara>
 
-            <title>Configuration version information in <literal>ndbinfo.nodes</literal></title>
+            <title>Configuration version information in <literal role="ndbinfo">ndbinfo.nodes</literal></title>
 
             <para>
               You can see which version or versions of the MySQL Cluster
               configuration file are in effect on the data nodes by
               checking the <literal>config_generation</literal> column
-              which is added to the <literal>ndbinfo.nodes</literal>
+              which is added to the <literal role="ndbinfo">ndbinfo.nodes</literal>
               table in MySQL Cluster NDB 7.1.13. For more information,
               see <xref linkend="mysql-cluster-ndbinfo-nodes"/>.
             </para>

@@ -2292,13 +2292,13 @@
         <listitem>
           <formalpara>
 
-            <title>Configuration version information in <literal>ndbinfo.nodes</literal></title>
+            <title>Configuration version information in <literal role="ndbinfo">ndbinfo.nodes</literal></title>
 
             <para>
               You can see which version or versions of the MySQL Cluster
               configuration file are in effect on the data nodes by
               checking the <literal>config_generation</literal> column
-              which is added to the <literal>ndbinfo.nodes</literal>
+              which is added to the <literal role="ndbinfo">ndbinfo.nodes</literal>
               table in MySQL Cluster NDB 7.1.13. For more information,
               see <xref linkend="mysql-cluster-ndbinfo-nodes"/>.
             </para>

@@ -3352,13 +3352,13 @@
         <listitem>
           <formalpara>
 
-            <title>Configuration version information in <literal>ndbinfo.nodes</literal></title>
+            <title>Configuration version information in <literal role="ndbinfo">ndbinfo.nodes</literal></title>
 
             <para>
               You can see which version or versions of the MySQL Cluster
               configuration file are in effect on the data nodes by
               checking the <literal>config_generation</literal> column
-              which is added to the <literal>ndbinfo.nodes</literal>
+              which is added to the <literal role="ndbinfo">ndbinfo.nodes</literal>
               table in MySQL Cluster NDB 7.0.24. For more information,
               see <xref linkend="mysql-cluster-ndbinfo-nodes"/>.
             </para>


Modified: trunk/refman-5.1/renamed-nodes.txt
===================================================================
--- trunk/refman-5.1/renamed-nodes.txt	2011-04-27 09:45:12 UTC (rev 26030)
+++ trunk/refman-5.1/renamed-nodes.txt	2011-04-27 12:17:30 UTC (rev 26031)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 0; 826 bytes

@@ -107,6 +107,7 @@
 mysql-cluster-ndbd-command-options mysql-cluster-programs-ndbd 2010-05-05
 mysql-cluster-ndbd-process mysql-cluster-programs-ndbd 2010-05-05
 mysql-cluster-ndbmtd-process mysql-cluster-programs-ndbmtd 2010-05-05
+mysql-cluster-ndbinfo-config_params mysql-cluster-ndbinfo-config-params 2012-04-27
 mysql-cluster-news-5-1-41-ndb-6-2-19 mysql-cluster-news-5-1-51-ndb-6-2-19 2011-03-15
 mysql-cluster-news-5-1-41-ndb-6-3-33 mysql-cluster-news-5-1-44-ndb-6-3-33 2011-03-15
 mysql-cluster-news-5-1-41-ndb-7-0-14 mysql-cluster-news-5-1-44-ndb-7-0-14 2011-03-15


Thread
svn commit - mysqldoc@oter02: r26031 - in trunk: dynamic-docs/changelog ndbapi refman-5.1jon.stephens27 Apr