List:Commits« Previous MessageNext Message »
From:jon Date:April 25 2007 9:09am
Subject:svn commit - mysqldoc@docsrva: r6172 - trunk/refman-5.1
View as plain text  
Author: jstephens
Date: 2007-04-25 09:09:12 +0200 (Wed, 25 Apr 2007)
New Revision: 6172

Log:

Entity additions for MCCGE versions



Modified:
   trunk/refman-5.1/mysql-cluster-mccge.xml
   trunk/refman-5.1/versions.ent


Modified: trunk/refman-5.1/mysql-cluster-mccge.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-mccge.xml	2007-04-24 23:33:48 UTC (rev 6171)
+++ trunk/refman-5.1/mysql-cluster-mccge.xml	2007-04-25 07:09:12 UTC (rev 6172)
Changed blocks: 47, Lines Added: 54, Lines Deleted: 54; 21372 bytes

@@ -55,7 +55,7 @@
   </indexterm>
 
   <para>
-    MySQL &current-series; is currently available and supported on a
+    MySQL &current-series-mccge; is currently available and supported on a
     number of platforms, including Linux, Solaris, Mac OS X, BSD, HP-UX,
     and many other Unix-style operating systems on a variety of
     hardware. For exact levels of support available for on specific

@@ -67,7 +67,7 @@
   </para>
 
   <para>
-    Like the standard version of MySQL Cluster, MySQL &current-series;
+    Like the standard version of MySQL Cluster, MySQL &current-series-mccge;
     is <emphasis>not</emphasis> currently supported on Microsoft
     Windows. We are working to make MySQL Cluster available on all
     operating systems supported by MySQL, including Windows.

@@ -75,7 +75,7 @@
 
   <para>
     This chapter represents a work in progress, and its contents are
-    subject to revision as MySQL &current-series; continues to evolve.
+    subject to revision as MySQL &current-series-mccge; continues to evolve.
     Additional information can be found on the MySQL AB web site at
     <ulink url="http://www.mysql.com/products/database/clustercge/"/>.
   </para>

@@ -974,7 +974,7 @@
         applications, or configuration to support MySQL Cluster. For
         supported operating systems, a standard installation should be
         sufficient. The MySQL software requirements are simple: all that
-        is needed is to build the server from the MySQL &current-series;
+        is needed is to build the server from the MySQL &current-series-mccge;
         source code with the appropriate options.
       </para>
 

@@ -1587,14 +1587,14 @@
 Cluster Configuration
 ---------------------
 [ndbd(NDB)]     2 node(s)
-id=2    @192.168.0.30  (Version: &current-version;, Nodegroup: 0, Master)
-id=3    @192.168.0.40  (Version: &current-version;, Nodegroup: 0)
+id=2    @192.168.0.30  (Version: &current-version-mccge;, Nodegroup: 0, Master)
+id=3    @192.168.0.40  (Version: &current-version-mccge;, Nodegroup: 0)
 
 [ndb_mgmd(MGM)] 1 node(s)
-id=1    @192.168.0.10  (Version: &current-version;)
+id=1    @192.168.0.10  (Version: &current-version-mccge;)
 
 [mysqld(SQL)]   1 node(s)
-id=4   (Version: &current-version;)
+id=4   (Version: &current-version-mccge;)
 </programlisting>
 
       <para>

@@ -1802,7 +1802,7 @@
 
       <para>
         It is important to note that <literal>NDB Cluster</literal> in
-        MySQL &current-series; does not support autodiscovery of
+        MySQL &current-series-mccge; does not support autodiscovery of
         databases. (See <xref linkend="mysql-cluster-limitations"/>.)
         This means that, once the <literal>world</literal> database and
         its tables have been created on one data node, you need to issue

@@ -1825,7 +1825,7 @@
 shell&gt; <userinput>mysql -u root -p</userinput>
 Enter password:
 Welcome to the MySQL monitor.  Commands end with ; or \g.
-Your MySQL connection id is 1 to server version: &current-version;
+Your MySQL connection id is 1 to server version: &current-version-mccge;
 
 Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
 

@@ -2131,7 +2131,7 @@
       </indexterm>
 
       <para>
-        When building MySQL &current-series; from source, be sure to use
+        When building MySQL &current-series-mccge; from source, be sure to use
         the <option>--with-ndbcluster</option> option when running
         <command>configure</command>. You can also use the
         <command>BUILD/compile-pentium-max</command> build script;

@@ -2144,14 +2144,14 @@
           <command>BUILD/compile-pentium-max</command> by default builds
           the MySQL Server with support for the
           <literal>InnoDB</literal> storage engine. <emphasis>You must
-          not deploy or make use of MySQL &current-series; employing the
+          not deploy or make use of MySQL &current-series-mccge; employing the
           <literal>InnoDB</literal> storage engine without prior written
           permission to do so from MySQL AB</emphasis>.
         </para>
 
         <para>
           If you wish to use <literal>InnoDB</literal> technology in
-          conjunction with your use of MySQL &current-series; and do not
+          conjunction with your use of MySQL &current-series-mccge; and do not
           already have authorization to do so as part of your MySQL
           Server license, contact your MySQL AB salesperson or other
           authorized MySQL AB representative for assistance in upgrading

@@ -2388,7 +2388,7 @@
 <programlisting>
 shell&gt; <userinput>mysql</userinput>
 Welcome to the MySQL monitor.  Commands end with ; or \g.
-Your MySQL connection id is 1 to server version: &current-version;
+Your MySQL connection id is 1 to server version: &current-version-mccge;
 
 Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
 

@@ -2570,7 +2570,7 @@
 <programlisting>
 # my.cnf
 # example additions to my.cnf for MySQL Cluster
-# (valid in MySQL &current-series;)
+# (valid in MySQL &current-series-mccge;)
 
 # enable ndbcluster storage engine, and provide connectstring for
 # management server host (default port is 1186)

@@ -2796,7 +2796,7 @@
           <listitem>
             <para>
               <literal>[SHM]</literal>: Defines shared-memory
-              connections between nodes. In MySQL &current-series;, it
+              connections between nodes. In MySQL &current-series-mccge;, it
               is enabled by default, but should still be considered
               experimental. For a discussion of SHM interconnects, see
               <xref linkend="mysql-cluster-shm-definition"/>.

@@ -4721,7 +4721,7 @@
             </para>
 
             <para>
-              This parameter is deprecated in MySQL &current-series;;
+              This parameter is deprecated in MySQL &current-series-mccge;;
               you should use <literal>MaxNoOfOrderedIndexes</literal>
               and <literal>MaxNoOfUniqueHashIndexes</literal> instead.
             </para>

@@ -5582,7 +5582,7 @@
           <literal>UndoIndexBuffer</literal> and
           <literal>UndoDataBuffer</literal> parameters which appeared in
           earlier versions of MySQL Cluster are no longer necessary in
-          MySQL &current-series;.
+          MySQL &current-series-mccge;.
         </para>
 
         <para id="mysql-cluster-controlling-log-messages">

@@ -6548,7 +6548,7 @@
           <emphasis role="bold">Important</emphasis>: <emphasis>SHM
           functionality is considered experimental only</emphasis>. It
           is not officially supported in any MySQL release series up to
-          and including &current-series;. This means that you must
+          and including &current-series-mccge;. This means that you must
           determine for yourself or by using our free resources (forums,
           mailing lists) whether it can be made to work correctly in
           your specific case.

@@ -8961,7 +8961,7 @@
           <manvolnum>1</manvolnum>
           <refmiscinfo class="manual">MySQL Database System</refmiscinfo>
           <refmiscinfo class="source">MySQL</refmiscinfo>
-          <refmiscinfo class="version">&current-series;</refmiscinfo>
+          <refmiscinfo
class="version">&current-series-mccge;</refmiscinfo>
           <refmiscinfo class="refman">The Storage Engine Node
Process</refmiscinfo>
         </refmeta>
 

@@ -9203,7 +9203,7 @@
             <command>ndbd</command> processes which belong to different
             node groups; however, such a configuration is still
             considered experimental and is not supported for MySQL
-            &current-series; in a production setting. See
+            &current-series-mccge; in a production setting. See
             <xref linkend="mysql-cluster-limitations"/>.
           </para>
 

@@ -9249,7 +9249,7 @@
           <manvolnum>1</manvolnum>
           <refmiscinfo class="manual">MySQL Database System</refmiscinfo>
           <refmiscinfo class="source">MySQL</refmiscinfo>
-          <refmiscinfo class="version">&current-series;</refmiscinfo>
+          <refmiscinfo
class="version">&current-series-mccge;</refmiscinfo>
           <refmiscinfo class="refman">The Management Server
Process</refmiscinfo>
         </refmeta>
 

@@ -9418,7 +9418,7 @@
           <manvolnum>1</manvolnum>
           <refmiscinfo class="manual">MySQL Database System</refmiscinfo>
           <refmiscinfo class="source">MySQL</refmiscinfo>
-          <refmiscinfo class="version">&current-series;</refmiscinfo>
+          <refmiscinfo
class="version">&current-series-mccge;</refmiscinfo>
           <refmiscinfo class="refman">The Management Client
Process</refmiscinfo>
         </refmeta>
 

@@ -10746,7 +10746,7 @@
           </para>
 
           <para>
-            It is not possible in MySQL &current-series; for data nodes
+            It is not possible in MySQL &current-series-mccge; for data nodes
             to join the cluster while it is running in single user mode.
             (See Bug #20395 for more information.)
           </para>

@@ -13074,7 +13074,7 @@
           <manvolnum>1</manvolnum>
           <refmiscinfo class="manual">MySQL Database System</refmiscinfo>
           <refmiscinfo class="source">MySQL</refmiscinfo>
-          <refmiscinfo class="version">&current-series;</refmiscinfo>
+          <refmiscinfo
class="version">&current-series-mccge;</refmiscinfo>
           <refmiscinfo class="refman">Restore a Cluster Backup</refmiscinfo>
         </refmeta>
 

@@ -13699,7 +13699,7 @@
       applications using the <literal>NDB</literal> API. The source code
       for most of these programs may be found in the
       <filename>storage/ndb/tools</filename> directory of the MySQL
-      &current-series; tree (see <xref linkend="installing-source"/>).
+      &current-series-mccge; tree (see <xref linkend="installing-source"/>).
       The <literal>NDB</literal> API is not covered in this manual;
       please refer to the
       <ulink
url="&base-url-docs;/ndbapi/en/"><literal>NDB</literal> API

@@ -13974,7 +13974,7 @@
           <manvolnum>1</manvolnum>
           <refmiscinfo class="manual">MySQL Database System</refmiscinfo>
           <refmiscinfo class="source">MySQL</refmiscinfo>
-          <refmiscinfo class="version">&current-series;</refmiscinfo>
+          <refmiscinfo
class="version">&current-series-mccge;</refmiscinfo>
           <refmiscinfo class="refman">Extract NDB Configuration
Information</refmiscinfo>
         </refmeta>
 

@@ -14465,7 +14465,7 @@
           <manvolnum>1</manvolnum>
           <refmiscinfo class="manual">MySQL Database System</refmiscinfo>
           <refmiscinfo class="source">MySQL</refmiscinfo>
-          <refmiscinfo class="version">&current-series;</refmiscinfo>
+          <refmiscinfo
class="version">&current-series-mccge;</refmiscinfo>
           <refmiscinfo class="refman">Extract NDB Configuration
Information</refmiscinfo>
         </refmeta>
 

@@ -14511,7 +14511,7 @@
             The source files for <command>ndb_cpcd</command> may be
             found in the directory
             <filename>storage/ndb/src/cw/cpcd</filename>, in the MySQL
-            &current-series; source tree.
+            &current-series-mccge; source tree.
           </para>
 
         </refsection>

@@ -14536,7 +14536,7 @@
           <manvolnum>1</manvolnum>
           <refmiscinfo class="manual">MySQL Database System</refmiscinfo>
           <refmiscinfo class="source">MySQL</refmiscinfo>
-          <refmiscinfo class="version">&current-series;</refmiscinfo>
+          <refmiscinfo
class="version">&current-series-mccge;</refmiscinfo>
           <refmiscinfo class="refman">Delete All Rows from NDB
Table</refmiscinfo>
         </refmeta>
 

@@ -14638,7 +14638,7 @@
           <manvolnum>1</manvolnum>
           <refmiscinfo class="manual">MySQL Database System</refmiscinfo>
           <refmiscinfo class="source">MySQL</refmiscinfo>
-          <refmiscinfo class="version">&current-series;</refmiscinfo>
+          <refmiscinfo
class="version">&current-series-mccge;</refmiscinfo>
           <refmiscinfo class="refman">Describe NDB Tables</refmiscinfo>
         </refmeta>
 

@@ -14794,7 +14794,7 @@
           <manvolnum>1</manvolnum>
           <refmiscinfo class="manual">MySQL Database System</refmiscinfo>
           <refmiscinfo class="source">MySQL</refmiscinfo>
-          <refmiscinfo class="version">&current-series;</refmiscinfo>
+          <refmiscinfo
class="version">&current-series-mccge;</refmiscinfo>
           <refmiscinfo class="refman">Drop Index from NDB Table</refmiscinfo>
         </refmeta>
 

@@ -14916,7 +14916,7 @@
           <manvolnum>1</manvolnum>
           <refmiscinfo class="manual">MySQL Database System</refmiscinfo>
           <refmiscinfo class="source">MySQL</refmiscinfo>
-          <refmiscinfo class="version">&current-series;</refmiscinfo>
+          <refmiscinfo
class="version">&current-series-mccge;</refmiscinfo>
           <refmiscinfo class="refman">Drop NDB Table</refmiscinfo>
         </refmeta>
 

@@ -14987,7 +14987,7 @@
           <manvolnum>1</manvolnum>
           <refmiscinfo class="manual">MySQL Database System</refmiscinfo>
           <refmiscinfo class="source">MySQL</refmiscinfo>
-          <refmiscinfo class="version">&current-series;</refmiscinfo>
+          <refmiscinfo
class="version">&current-series-mccge;</refmiscinfo>
           <refmiscinfo class="refman">NDB Error-Reporting
Utility</refmiscinfo>
         </refmeta>
 

@@ -15071,7 +15071,7 @@
           <manvolnum>1</manvolnum>
           <refmiscinfo class="manual">MySQL Database System</refmiscinfo>
           <refmiscinfo class="source">MySQL</refmiscinfo>
-          <refmiscinfo class="version">&current-series;</refmiscinfo>
+          <refmiscinfo
class="version">&current-series-mccge;</refmiscinfo>
           <refmiscinfo class="refman">Print NDB Backup File
Contents</refmiscinfo>
         </refmeta>
 

@@ -15161,7 +15161,7 @@
           <manvolnum>1</manvolnum>
           <refmiscinfo class="manual">MySQL Database System</refmiscinfo>
           <refmiscinfo class="source">MySQL</refmiscinfo>
-          <refmiscinfo class="version">&current-series;</refmiscinfo>
+          <refmiscinfo
class="version">&current-series-mccge;</refmiscinfo>
           <refmiscinfo class="refman">Print NDB Schema File
Contents</refmiscinfo>
         </refmeta>
 

@@ -15247,7 +15247,7 @@
           <manvolnum>1</manvolnum>
           <refmiscinfo class="manual">MySQL Database System</refmiscinfo>
           <refmiscinfo class="source">MySQL</refmiscinfo>
-          <refmiscinfo class="version">&current-series;</refmiscinfo>
+          <refmiscinfo
class="version">&current-series-mccge;</refmiscinfo>
           <refmiscinfo class="refman">Print NDB System File
Contents</refmiscinfo>
         </refmeta>
 

@@ -15494,7 +15494,7 @@
           <manvolnum>1</manvolnum>
           <refmiscinfo class="manual">MySQL Database System</refmiscinfo>
           <refmiscinfo class="source">MySQL</refmiscinfo>
-          <refmiscinfo class="version">&current-series;</refmiscinfo>
+          <refmiscinfo
class="version">&current-series-mccge;</refmiscinfo>
           <refmiscinfo class="refman">Print Rows from NDB Table</refmiscinfo>
         </refmeta>
 

@@ -15934,7 +15934,7 @@
           <manvolnum>1</manvolnum>
           <refmiscinfo class="manual">MySQL Database System</refmiscinfo>
           <refmiscinfo class="source">MySQL</refmiscinfo>
-          <refmiscinfo class="version">&current-series;</refmiscinfo>
+          <refmiscinfo
class="version">&current-series-mccge;</refmiscinfo>
           <refmiscinfo class="refman">Print Row Counts for NDB
Tables</refmiscinfo>
         </refmeta>
 

@@ -16013,7 +16013,7 @@
           <manvolnum>1</manvolnum>
           <refmiscinfo class="manual">MySQL Database System</refmiscinfo>
           <refmiscinfo class="source">MySQL</refmiscinfo>
-          <refmiscinfo class="version">&current-series;</refmiscinfo>
+          <refmiscinfo
class="version">&current-series-mccge;</refmiscinfo>
           <refmiscinfo class="refman">Display List of NDB
Tables</refmiscinfo>
         </refmeta>
 

@@ -16211,7 +16211,7 @@
           <manvolnum>1</manvolnum>
           <refmiscinfo class="manual">MySQL Database System</refmiscinfo>
           <refmiscinfo class="source">MySQL</refmiscinfo>
-          <refmiscinfo class="version">&current-series;</refmiscinfo>
+          <refmiscinfo
class="version">&current-series-mccge;</refmiscinfo>
           <refmiscinfo class="refman">NDBCluster Size Requirement
Estimator</refmiscinfo>
         </refmeta>
 

@@ -16425,7 +16425,7 @@
           <manvolnum>1</manvolnum>
           <refmiscinfo class="manual">MySQL Database System</refmiscinfo>
           <refmiscinfo class="source">MySQL</refmiscinfo>
-          <refmiscinfo class="version">&current-series;</refmiscinfo>
+          <refmiscinfo
class="version">&current-series-mccge;</refmiscinfo>
           <refmiscinfo class="refman">Wait for Cluster to Reach a Given
Status</refmiscinfo>
         </refmeta>
 

@@ -17199,7 +17199,7 @@
         <important>
           <para>
             See <xref linkend="news-5-1-15-ndb-6-1-5"/>, before
-            upgrading from a previous &current-series; or mainline MySQL
+            upgrading from a previous &current-series-mccge; or mainline MySQL
             5.1 release.
           </para>
         </important>

@@ -19772,16 +19772,16 @@
 
     <para>
       In this section, we provide a list of known limitations in MySQL
-      Cluster releases in the &current-series;.x series compared to
+      Cluster releases in the &current-series-mccge;.x series compared to
       features available when using the <literal>MyISAM</literal> and
       <literal>InnoDB</literal> 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
+      &current-series-mccge;; however, we will attempt to supply fixes for
       these issues in subsequent release series. If you check the
       <quote>Cluster</quote> category in the MySQL bugs database at
       <ulink url="http://bugs.mysql.com"/>, you can find known bugs
-      which (if marked <quote>&current-series;</quote>) we intend to
-      correct in upcoming releases of MySQL &current-series;.
+      which (if marked <quote>&current-series-mccge;</quote>) we intend
to
+      correct in upcoming releases of MySQL &current-series-mccge;.
     </para>
 
     <para>

@@ -19789,7 +19789,7 @@
       conditions just set forth. You can report any discrepancies that
       you encounter to the MySQL bugs database using the instructions
       given in <xref linkend="bug-reports"/>. If we do not plan to fix
-      the problem in MySQL &current-series;, we will add it to the list.
+      the problem in MySQL &current-series-mccge;, we will add it to the list.
     </para>
 
     <para>

@@ -19861,7 +19861,7 @@
             <para>
               Geometry datatypes (<literal>WKT</literal> and
               <literal>WKB</literal>) are supported in
-              <literal>NDB</literal> tables in MySQL &current-series;.
+              <literal>NDB</literal> tables in MySQL
&current-series-mccge;.
               However, spatial indexes are not supported.
             </para>
           </listitem>

@@ -19910,7 +19910,7 @@
 
             <para>
               Support for user-defined partitioning for MySQL Cluster in
-              MySQL &current-series; is restricted to
+              MySQL &current-series-mccge; is restricted to
               [<literal>LINEAR</literal>] <literal>KEY</literal>
               partitioning. Beginning with MySQL 5.1.12, using any other
               partitioning type with <literal>ENGINE=NDB</literal> or

@@ -20674,7 +20674,7 @@
               concurrently on a single host, it is not always advisable
               to do so for reasons of performance and high availability,
               as well as other considerations. In particular, we do not
-              in MySQL &current-series; support for production use any
+              in MySQL &current-series-mccge; support for production use any
               MySQL Cluster deployment in which more than one
               <command>ndbd</command> process is run on a single
               physical machine.

@@ -20683,7 +20683,7 @@
             <para>
               We may support multiple data nodes per host in a future
               MySQL release, following additional testing. However, in
-              MySQL &current-series;, such configurations can be
+              MySQL &current-series-mccge;, such configurations can be
               considered experimental only.
             </para>
           </listitem>

@@ -20970,7 +20970,7 @@
 
     <para>
       In this section, we discuss changes in the implementation of MySQL
-      Cluster in MySQL &current-series; as compared to MySQL
+      Cluster in MySQL &current-series-mccge; as compared to MySQL
       &previous-series;.
 
 <!-- We will also discuss our roadmap for further

@@ -21057,7 +21057,7 @@
 
           <para>
             For additional general information about user-defined
-            partitioning in MySQL &current-series;, see
+            partitioning in MySQL &current-series-mccge;, see
             <xref linkend="partitioning"/>. Specifics of partitioning
             types are discussed in <xref linkend="partitioning-types"/>.
           </para>


Modified: trunk/refman-5.1/versions.ent
===================================================================
--- trunk/refman-5.1/versions.ent	2007-04-24 23:33:48 UTC (rev 6171)
+++ trunk/refman-5.1/versions.ent	2007-04-25 07:09:12 UTC (rev 6172)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 1; 1091 bytes

@@ -5,7 +5,9 @@
 -->
 <!ENTITY title-refman-previous "MySQL 5.0 Reference Manual"><!-- Title of Manual
previous edition  -->
 <!ENTITY current-series "5.1"><!-- Current MySQL release series  -->
+<!ENTITY current-series-mccge "Cluster 5.1 Carrier Grade Edition"><!-- Current
MySQL CGE release series  -->
 <!ENTITY previous-series "5.0"><!-- Previous MySQL release series  -->
 <!ENTITY next-series "5.2"><!-- Next MySQL release series  -->
-<!ENTITY current-version "5.1.18-beta"><!-- Current MySQL Version - update with
new releases -->
+<!ENTITY current-version "5.1.18-beta"><!-- Current MySQL version - update with
new releases -->
+<!ENTITY current-version "5.1.15-ndb-6.1.6-beta"><!-- Current MySQL CGE version
- update with new releases -->
 <!ENTITY current-maturity "beta"><!-- Current maturity level: alpha, beta,
release candidate, production  -->


Thread
svn commit - mysqldoc@docsrva: r6172 - trunk/refman-5.1jon25 Apr