Author: jstephens
Date: 2009-01-23 12:23:15 +0100 (Fri, 23 Jan 2009)
New Revision: 13360
Log:
1. Some restructuring... Moving material relating to NDB API into one
chapter, demoting former chapters to sections.
2. <literal>NDB</literal> API -> NDB API
3. Edited/updated book intro
4. Updated dependencies
Modified:
trunk/mysql-monitor-2.0/Makefile.depends
trunk/mysqlqb/Makefile.depends
trunk/ndbapi/class-column.xml
trunk/ndbapi/class-datafile.xml
trunk/ndbapi/class-event.xml
trunk/ndbapi/class-index.xml
trunk/ndbapi/class-logfilegroup.xml
trunk/ndbapi/class-ndb-cluster-connection.xml
trunk/ndbapi/class-ndb.xml
trunk/ndbapi/class-ndbdictionary.xml
trunk/ndbapi/class-ndbeventoperation.xml
trunk/ndbapi/class-ndboperation.xml
trunk/ndbapi/class-ndbrecattr.xml
trunk/ndbapi/class-ndbscanoperation.xml
trunk/ndbapi/class-ndbtransaction.xml
trunk/ndbapi/class-table.xml
trunk/ndbapi/class-tablespace.xml
trunk/ndbapi/class-undofile.xml
trunk/ndbapi/getting-started.xml
trunk/ndbapi/interface-ndbrecord.xml
trunk/ndbapi/ndb-classes.xml
trunk/ndbapi/ndb-error-codes.xml
trunk/ndbapi/ndb-errors.xml
trunk/ndbapi/ndb-examples.xml
trunk/ndbapi/ndb-hierarchy.xml
trunk/ndbapi/ndb-internals.xml
trunk/ndbapi/ndbapi.xml
trunk/refman-5.1-maria/Makefile.depends
trunk/refman-5.1/Makefile.depends
trunk/refman-6.0/Makefile.depends
Modified: trunk/mysql-monitor-2.0/Makefile.depends
===================================================================
--- trunk/mysql-monitor-2.0/Makefile.depends 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/mysql-monitor-2.0/Makefile.depends 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 0; 776 bytes
@@ -276,6 +276,8 @@
dynxml_local_monitor_faq_IMAGES =
dynxml_local_monitor_faq_SOURCES = dynxml-local-monitor-faq.xml $(dynxml_local_monitor_faq_INCLUDES)
dynxml_local_monitor_faq_IDMAPS = \
+ ../mysql-monitor-2.0/metadata/dashboard-query-analysis.idmap \
+ ../mysql-monitor-2.0/metadata/deployment.idmap \
../mysql-monitor-2.0/metadata/monitor-faq-core.idmap
dynxml-local-monitor-faq.validpure: $(dynxml_local_monitor_faq_SOURCES)
dynxml-local-monitor-faq.titles: $(dynxml_local_monitor_faq_SOURCES)
Modified: trunk/mysqlqb/Makefile.depends
===================================================================
--- trunk/mysqlqb/Makefile.depends 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/mysqlqb/Makefile.depends 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 575 bytes
@@ -67,7 +67,7 @@
../refman-5.0/metadata/views.idmap \
../refman-common/metadata/bug-reports.idmap \
../refman-common/metadata/credits.idmap \
- metadata/mysqlqb_functions.idmap
+ ../refman-common/metadata/regexp.idmap
mysqlqb.validpure: $(mysqlqb_SOURCES)
mysqlqb.titles: $(mysqlqb_SOURCES)
mysqlqb.useless: $(mysqlqb_SOURCES)
Modified: trunk/ndbapi/class-column.xml
===================================================================
--- trunk/ndbapi/class-column.xml 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/ndbapi/class-column.xml 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 4, Lines Added: 4, Lines Deleted: 4; 1752 bytes
@@ -86,7 +86,7 @@
These types in general correspond to MySQL datatypes and their
variants. The data formats are same as in MySQL. The
- <literal>NDB</literal> API provides no support for constructing
+ NDB API provides no support for constructing
such formats; however, they are checked by the
<literal>NDB</literal> kernel.
</para>
@@ -722,7 +722,7 @@
<para>
As with other database objects, <literal>Column</literal> object
creation and attribute changes to existing columns done using
- the <literal>NDB</literal> API are not visible from MySQL. For
+ the NDB API are not visible from MySQL. For
example, if you change a column's datatype using
<literal>Column::setType()</literal>, MySQL will regard the type
of column as being unchanged. The only exception to this rule
@@ -754,7 +754,7 @@
<warning>
<para>
A <literal>Column</literal> created using the
- <literal>NDB</literal> API will <emphasis>not</emphasis> be
+ NDB API will <emphasis>not</emphasis> be
visible to a MySQL server.
</para>
@@ -2302,7 +2302,7 @@
<literal>setName()</literal> is the only
<literal>Column</literal> method whose result is visible from
a MySQL Server. MySQL cannot see any other changes made to
- existing columns using the <literal>NDB</literal> API.
+ existing columns using the NDB API.
</para>
</important>
Modified: trunk/ndbapi/class-datafile.xml
===================================================================
--- trunk/ndbapi/class-datafile.xml 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/ndbapi/class-datafile.xml 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 605 bytes
@@ -61,7 +61,7 @@
Versions of MySQL prior to 5.1 do not support Disk Data storage
and so do not support datafiles; thus the
<literal>Datafile</literal> class is unavailable for
- <literal>NDB</literal> API applications written against these
+ NDB API applications written against these
MySQL versions.
</para>
</note>
Modified: trunk/ndbapi/class-event.xml
===================================================================
--- trunk/ndbapi/class-event.xml 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/ndbapi/class-event.xml 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 501 bytes
@@ -276,7 +276,7 @@
<para>
<literal>TableEvent</literal> is used to classify the types of
events that may be associated with tables in the
- <literal>NDB</literal> API.
+ NDB API.
</para>
</formalpara>
Modified: trunk/ndbapi/class-index.xml
===================================================================
--- trunk/ndbapi/class-index.xml 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/ndbapi/class-index.xml 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 492 bytes
@@ -305,7 +305,7 @@
<important>
<para>
- Indexes created using the <literal>NDB</literal> API cannot be
+ Indexes created using the NDB API cannot be
seen by the MySQL Server.
</para>
</important>
Modified: trunk/ndbapi/class-logfilegroup.xml
===================================================================
--- trunk/ndbapi/class-logfilegroup.xml 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/ndbapi/class-logfilegroup.xml 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 626 bytes
@@ -64,7 +64,7 @@
Versions of MySQL prior to 5.1 do not support Disk Data storage
and so do not support logfile groups; thus the
<literal>LogfileGroup</literal> class is unavailable for
- <literal>NDB</literal> API applications written against these
+ NDB API applications written against these
MySQL versions.
</para>
</note>
Modified: trunk/ndbapi/class-ndb-cluster-connection.xml
===================================================================
--- trunk/ndbapi/class-ndb-cluster-connection.xml 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/ndbapi/class-ndb-cluster-connection.xml 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 716 bytes
@@ -294,7 +294,7 @@
to a cluster of data nodes. The object returned by this method
is required in order to instantiate an <literal>Ndb</literal>
object. (See <xref linkend="class-ndb"/>.) Thus, every
- <literal>NDB</literal> API application requires the use of an
+ NDB API application requires the use of an
<literal>Ndb_cluster_connection</literal>.
</para>
Modified: trunk/ndbapi/class-ndb.xml
===================================================================
--- trunk/ndbapi/class-ndb.xml 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/ndbapi/class-ndb.xml 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 8, Lines Added: 8, Lines Deleted: 8; 3113 bytes
@@ -15,7 +15,7 @@
<para>
This class represents the <literal>NDB</literal> kernel; it is the
- primary class of the <literal>NDB</literal> API.
+ primary class of the NDB API.
</para>
</abstract>
@@ -45,7 +45,7 @@
<title>Description</title>
<para>
- Any non-trivial <literal>NDB</literal> API program makes use of at
+ Any non-trivial NDB API program makes use of at
least one instance of <literal>Ndb</literal>. By using several
<literal>Ndb</literal> objects, it is possible to implement a
multi-threaded application. You should remember that one
@@ -222,7 +222,7 @@
<para>
This creates an instance of <literal>Ndb</literal>, which
represents a connection to the MySQL Cluster. All
- <literal>NDB</literal> API applications should begin with the
+ NDB API applications should begin with the
creation of at least one <literal>Ndb</literal> object. This
requires the creation of at least one instance of
<literal>Ndb_cluster_connection</literal>, which serves as a
@@ -1182,7 +1182,7 @@
<title>Description</title>
<para>
- This is one of two <literal>NDB</literal> API methods provided
+ This is one of two NDB API methods provided
for closing a transaction (the other being
<literal>NdbTransaction::close()</literal> — see
<xref linkend="class-ndbtransaction-close"/>). You must call
@@ -1646,7 +1646,7 @@
This method provides you with two different ways to obtain an
<literal>NdbError</literal> object representing an error
condition. For more detailed information about error handling
- in the <literal>NDB</literal> API, see
+ in the NDB API, see
<xref linkend="ndb-errors"/>.
</para>
@@ -1680,7 +1680,7 @@
Regardless of which version of the method is used, the
<literal>NdbError</literal> object returned persists until the
- next <literal>NDB</literal> API method is invoked.
+ next NDB API method is invoked.
</para>
</formalpara>
@@ -1695,7 +1695,7 @@
obtain the error matching a specific
<replaceable>errorCode</replaceable>, invoke the method
passing the code (an <literal>int</literal>) to it as a
- parameter. For a listing of <literal>NDB</literal> API error
+ parameter. For a listing of NDB API error
codes and corresponding error messages, see
<xref linkend="ndb-error-messages"/>.
</para>
@@ -1723,7 +1723,7 @@
<para>
This example shows how to use
<literal>getNdbError()</literal> to retrieve the most recent
- <literal>NDB</literal> API error:
+ NDB API error:
<programlisting>
[<emphasis>To be supplied...</emphasis>]
Modified: trunk/ndbapi/class-ndbdictionary.xml
===================================================================
--- trunk/ndbapi/class-ndbdictionary.xml 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/ndbapi/class-ndbdictionary.xml 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 2, Lines Added: 3, Lines Deleted: 3; 1195 bytes
@@ -22,7 +22,7 @@
While the preferred method of database object creation and
deletion is through the MySQL Server,
<literal>NdbDictionary</literal> also permits the developer to
- perform these tasks via the <literal>NDB</literal> API.
+ perform these tasks via the NDB API.
</para>
</abstract>
@@ -114,10 +114,10 @@
</para>
<para>
- Dropping indexes via the <literal>NDB</literal> API that were
+ Dropping indexes via the NDB API that were
created originally from a MySQL Cluster causes inconsistencies. It
is possible that a table from which one or more indexes have been
- dropped using the <literal>NDB</literal> API will no longer be
+ dropped using the NDB API will no longer be
usable by MySQL following such operations. In this event, the
table must be dropped, and then re-created using MySQL to make it
accessible to MySQL once more.
Modified: trunk/ndbapi/class-ndbeventoperation.xml
===================================================================
--- trunk/ndbapi/class-ndbeventoperation.xml 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/ndbapi/class-ndbeventoperation.xml 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 1057 bytes
@@ -110,7 +110,7 @@
<para>
The following issues may be encountered when working with event
- operations in the <literal>NDB</literal> API:
+ operations in the NDB API:
<itemizedlist>
@@ -158,7 +158,7 @@
<para>
We intend to remedy this issue in a future release of MySQL
- Cluster and the <literal>NDB</literal> API.
+ Cluster and the NDB API.
</para>
</listitem>
@@ -585,7 +585,7 @@
<para>
This method defines the retrieval of an attribute value. The
- <literal>NDB</literal> API allocates memory for the
+ NDB API allocates memory for the
<literal>NdbRecAttr</literal> object that is to hold the
returned attribute value.
</para>
Modified: trunk/ndbapi/class-ndboperation.xml
===================================================================
--- trunk/ndbapi/class-ndboperation.xml 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/ndbapi/class-ndboperation.xml 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 1312 bytes
@@ -536,7 +536,7 @@
<para>
This method prepares for the retrieval of an attribute value.
- The <literal>NDB</literal> API allocates memory for an
+ The NDB API allocates memory for an
<literal>NdbRecAttr</literal> object that is later used to
hold the returned attribute value.
</para>
@@ -1611,7 +1611,7 @@
</para>
<para>
- However, the <literal>NDB</literal> API does check that the
+ However, the NDB API does check that the
application sends a correct length to the interface as given
in the length parameter. A <literal>char*</literal> value can
contain any datatype or any type of array. If the length is
@@ -1634,7 +1634,7 @@
<note>
<para>
When you use <literal>insertTuple()</literal>, the
- <literal>NDB</literal> API will automatically detect that it
+ NDB API will automatically detect that it
is supposed to use <literal>equal()</literal> instead.
</para>
Modified: trunk/ndbapi/class-ndbrecattr.xml
===================================================================
--- trunk/ndbapi/class-ndbrecattr.xml 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/ndbapi/class-ndbrecattr.xml 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1052 bytes
@@ -50,7 +50,7 @@
attribute value after it has been retrieved the
<literal>NDB</literal> Cluster using the
<literal>NdbOperation::getValue()</literal>. This object is
- allocated by the <literal>NDB</literal> API. A brief example is
+ allocated by the NDB API. A brief example is
shown here:
<programlisting>
@@ -1675,7 +1675,7 @@
This method is used to obtain a reference to an attribute
value, as a <literal>char</literal> pointer. This pointer is
aligned appropriately for the datatype. The memory is released
- by the <literal>NDB</literal> API when
+ by the NDB API when
<literal>NdbTransaction::closeTransaction()</literal> is
executed on the transaction which read the value.
</para>
Modified: trunk/ndbapi/class-ndbscanoperation.xml
===================================================================
--- trunk/ndbapi/class-ndbscanoperation.xml 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/ndbapi/class-ndbscanoperation.xml 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 972 bytes
@@ -487,7 +487,7 @@
<listitem>
<para>
- Normally, the <literal>NDB</literal> API contacts the
+ Normally, the NDB API contacts the
<literal>NDB</literal> kernel for more tuples whenever
it is necessary; setting
<replaceable>fetchAllowed</replaceable> to
@@ -517,7 +517,7 @@
to be made, and then, the locks to be released.
Following this, call <literal>nextResult(true)</literal>
— this fetches more records and caches them in the
- <literal>NDB</literal> API.
+ NDB API.
</para>
<note>
Modified: trunk/ndbapi/class-ndbtransaction.xml
===================================================================
--- trunk/ndbapi/class-ndbtransaction.xml 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/ndbapi/class-ndbtransaction.xml 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1195 bytes
@@ -45,7 +45,7 @@
<title>Description</title>
<para>
- A transaction is represented in the <literal>NDB</literal> API by
+ A transaction is represented in the NDB API by
an <literal>NdbTransaction</literal> object, which belongs to an
<literal>Ndb</literal> object and is created using
<literal>Ndb::startTransaction()</literal>. A transaction consists
@@ -476,7 +476,7 @@
Beginning with MySQL Cluster NDB 6.2.0, this type belongs to
the <literal>NdbOperation</literal> class and its possible
values and default behavior have changed.
- <literal>NDB</literal> API application code written against
+ NDB API application code written against
previous versions of MySQL Cluster that refers explicitly to
<literal>NdbTransaction::AbortOption</literal> values must be
modified to work with MySQL Cluster NDB 6.2.0 or later.
Modified: trunk/ndbapi/class-table.xml
===================================================================
--- trunk/ndbapi/class-table.xml 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/ndbapi/class-table.xml 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 4, Lines Added: 4, Lines Deleted: 4; 1589 bytes
@@ -15,7 +15,7 @@
<para>
This section describes the <literal>Table</literal> class, which
- models a database table in the <literal>NDB</literal> API.
+ models a database table in the NDB API.
</para>
</abstract>
@@ -55,7 +55,7 @@
<important>
<para>
- It is possible using the <literal>NDB</literal> API to create
+ It is possible using the NDB API to create
tables independently of the MySQL server. However, it is usually
not advisable to do so, since tables created in this fashion
cannot be seen by the MySQL server. Similarly, it is possible
@@ -513,7 +513,7 @@
<para>
As with other database objects, <literal>Table</literal> object
creation and attribute changes to existing tables done using the
- <literal>NDB</literal> API are not visible from MySQL. For
+ NDB API are not visible from MySQL. For
example, if you add a new column to a table using
<literal>Table::addColumn()</literal>, MySQL will not see the
new column. The only exception to this rule with regard to
@@ -540,7 +540,7 @@
<important>
<para>
- Tables created in the <literal>NDB</literal> API using this
+ Tables created in the NDB API using this
method are not accessible from MySQL.
</para>
</important>
Modified: trunk/ndbapi/class-tablespace.xml
===================================================================
--- trunk/ndbapi/class-tablespace.xml 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/ndbapi/class-tablespace.xml 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 860 bytes
@@ -65,7 +65,7 @@
Versions of MySQL prior to 5.1 do not support Disk Data storage
and so do not support tablespaces; thus the
<literal>Tablespace</literal> class is unavailable for
- <literal>NDB</literal> API applications written against these
+ NDB API applications written against these
MySQL versions.
</para>
</note>
@@ -204,7 +204,7 @@
<para>
This section provides details of the public members of the
- <literal>NDB</literal> API's <literal>Tablespace</literal>
+ NDB API's <literal>Tablespace</literal>
class.
</para>
Modified: trunk/ndbapi/class-undofile.xml
===================================================================
--- trunk/ndbapi/class-undofile.xml 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/ndbapi/class-undofile.xml 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 604 bytes
@@ -62,7 +62,7 @@
Versions of MySQL prior to 5.1 do not support Disk Data storage
and so do not support undofile; thus the
<literal>Undofile</literal> class is unavailable for
- <literal>NDB</literal> API applications written against these
+ NDB API applications written against these
MySQL versions.
</para>
</note>
Modified: trunk/ndbapi/getting-started.xml
===================================================================
--- trunk/ndbapi/getting-started.xml 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/ndbapi/getting-started.xml 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 11, Lines Added: 46, Lines Deleted: 53; 7269 bytes
@@ -1,42 +1,40 @@
<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
<!ENTITY % all.entities SYSTEM "all-entities.ent">
%all.entities;
]>
<!--
- <chapter id="tips-tricks-problems">
+ <section id="tips-tricks-problems">
- <title>TIPS, TRICKS, AND COMMON PROBLEMS</title>
+ <title>TIPS, TRICKS, AND COMMON PROBLEMS</title>
- <abstract>
+ <abstract>
- <para></para>
+ <para></para>
- </abstract>
+ </abstract>
+
+ </section>
-->
-<chapter id="getting-started">
+<section id="getting-started">
- <title>Getting Started with the <literal>NDB</literal> API</title>
+ <title>Getting Started with the NDB API</title>
- <abstract>
+ <para>
+ This section discusses preparations necessary for writing and
+ compiling an NDB API application.
+ </para>
- <para>
- This chapter discusses preparations for writing an
- <literal>NDB</literal> API application.
- </para>
-
- </abstract>
-
<section id="getting-started-compiling">
- <title>Compiling and Linking <literal>NDB</literal> API Programs</title>
+ <title>Compiling and Linking NDB API Programs</title>
<abstract>
<para>
- This section provides information on compiling and linking
- <literal>NDB</literal> API applications, including requirements
- and compiler and linker options.
+ This section provides information on compiling and linking NDB
+ API applications, including requirements and compiler and linker
+ options.
</para>
</abstract>
@@ -46,8 +44,8 @@
<title>General Requirements</title>
<para>
- To use the <literal>NDB</literal> API with MySQL, you must have
- the <literal>NDB</literal> client library and its header files
+ To use the NDB API with MySQL, you must have the
+ <literal>NDB</literal> client library and its header files
installed alongside the regular MySQL client libraries and
headers. These are automatically installed when you build MySQL
using the <option>--with-ndbcluster</option>
@@ -60,9 +58,8 @@
<para>
MySQL 4.1 does not install the required
<literal>NDB</literal>-specific header files. You should use
- MySQL 5.0 or later when writing <literal>NDB</literal> API
- applications, and this Guide is targeted for use with MySQL
- 5.1.
+ MySQL 5.0 or later when writing NDB API applications, and this
+ Guide is targeted for use with MySQL 5.1.
</para>
<para>
@@ -85,12 +82,11 @@
<title>Header Files</title>
<para>
- In order to compile source files that use the
- <literal>NDB</literal> API, you must ensure that the necessary
- header files can be found. Header files specific to the
- <literal>NDB</literal> API are installed in the following
- subdirectories of the MySQL <filename>include</filename>
- directory:
+ In order to compile source files that use the NDB API, you
+ must ensure that the necessary header files can be found.
+ Header files specific to the NDB API are installed in the
+ following subdirectories of the MySQL
+ <filename>include</filename> directory:
<itemizedlist>
@@ -127,7 +123,7 @@
</programlisting>
This sets the include path for the MySQL header files but not
- for those specific to the <literal>NDB</literal> API. The
+ for those specific to the NDB API. The
<option>--include</option> option to
<command>mysql_config</command> returns the generic include
path switch:
@@ -170,8 +166,8 @@
<title>Linker Options</title>
<para>
- <literal>NDB</literal> API applications must be linked against
- both the MySQL and <literal>NDB</literal> client libraries. The
+ NDB API applications must be linked against both the MySQL and
+ <literal>NDB</literal> client libraries. The
<literal>NDB</literal> client library also requires some
functions from the <literal>mystrings</literal> library, so this
must be linked in as well.
@@ -396,8 +392,8 @@
<abstract>
<para>
- This section covers connecting an <literal>NDB</literal> API
- application to a MySQL cluster.
+ This section covers connecting an NDB API application to a MySQL
+ cluster.
</para>
</abstract>
@@ -407,16 +403,15 @@
<title>Include Files</title>
<para>
- <literal>NDB</literal> API applications require one or more of
- the following include files:
+ NDB API applications require one or more of the following
+ include files:
<itemizedlist>
<listitem>
<para>
- Applications accessing Cluster data via the
- <literal>NDB</literal> API must include the file
- <filename>NdbApi.hpp</filename>.
+ Applications accessing Cluster data via the NDB API must
+ include the file <filename>NdbApi.hpp</filename>.
</para>
</listitem>
@@ -445,11 +440,10 @@
<title>API Initialisation and Cleanup</title>
<para>
- Before using the <literal>NDB</literal> API, it must first be
- initialised by calling the <literal>ndb_init()</literal>
- function. Once an <literal>NDB</literal> API application is
- complete, call <literal>ndb_end(0)</literal> to perform a
- cleanup.
+ Before using the NDB API, it must first be initialised by
+ calling the <literal>ndb_init()</literal> function. Once an NDB
+ API application is complete, call <literal>ndb_end(0)</literal>
+ to perform a cleanup.
</para>
</section>
@@ -589,12 +583,11 @@
<para>
Databases and schemas are not represented by objects as such in
- the <literal>NDB</literal> API. Instead, they are modelled as
- attributes of <literal>Table</literal> and
- <literal>Index</literal> objects. The value of the
- <literal>database</literal> attribute of one of these objects is
- always the same as the name of the MySQL database to which the
- table or index belongs. The value of the
+ the NDB API. Instead, they are modelled as attributes of
+ <literal>Table</literal> and <literal>Index</literal> objects.
+ The value of the <literal>database</literal> attribute of one of
+ these objects is always the same as the name of the MySQL
+ database to which the table or index belongs. The value of the
<literal>schema</literal> attribute of a
<literal>Table</literal> or <literal>Index</literal> object is
always '<literal>def</literal>' (for <quote>default</quote>).
@@ -865,4 +858,4 @@
</section>
-->
-</chapter>
+</section>
Modified: trunk/ndbapi/interface-ndbrecord.xml
===================================================================
--- trunk/ndbapi/interface-ndbrecord.xml 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/ndbapi/interface-ndbrecord.xml 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 825 bytes
@@ -55,10 +55,10 @@
<para>
An <literal>NdbRecord</literal> can be created in
- <literal>NDB</literal> API programs by calling the
+ NDB API programs by calling the
<literal>createRecord()</literal> method of the
<literal>NdbDictionary</literal> class. In addition, a number of
- <literal>NDB</literal> API methods have additional declarations in
+ NDB API methods have additional declarations in
MySQL Cluster NDB 6.2.3 and later MySQL Cluster NDB 6.x releases
that allow the programmer to leverage <literal>NdbRecord</literal>:
Modified: trunk/ndbapi/ndb-classes.xml
===================================================================
--- trunk/ndbapi/ndb-classes.xml 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/ndbapi/ndb-classes.xml 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 2, Lines Added: 8, Lines Deleted: 13; 1334 bytes
@@ -1,22 +1,17 @@
<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
<!ENTITY % all.entities SYSTEM "all-entities.ent">
%all.entities;
]>
-<chapter id="ndb-classes">
+<section id="ndb-classes">
- <title><literal>NDB</literal> API Classes, Interfaces, and Structures</title>
+ <title>NDB API Classes, Interfaces, and Structures</title>
- <abstract>
+ <para>
+ This section provides a detailed listing of all classes, interfaces,
+ and stuctures defined in the <literal>NDB</literal> API.
+ </para>
- <para>
- This chapter provides a detailed listing of all classes,
- interfaces, and stuctures defined in the <literal>NDB</literal>
- API.
- </para>
-
- </abstract>
-
<para>
Each listing includes:
@@ -133,4 +128,4 @@
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="struct-recordspecification.xml"/>
-</chapter>
+</section>
Modified: trunk/ndbapi/ndb-error-codes.xml
===================================================================
--- trunk/ndbapi/ndb-error-codes.xml 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/ndbapi/ndb-error-codes.xml 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 496 bytes
@@ -22,7 +22,7 @@
<para>
This section contains a number of tables, one for each type of
- <literal>NDB</literal> API error. The error types include the
+ NDB API error. The error types include the
following:
<informaltable>
Modified: trunk/ndbapi/ndb-errors.xml
===================================================================
--- trunk/ndbapi/ndb-errors.xml 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/ndbapi/ndb-errors.xml 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 5, Lines Added: 28, Lines Deleted: 33; 4979 bytes
@@ -13,10 +13,9 @@
potentially generated in MySQL Cluster API applications. It
includes information about error codes, classifications, and
messages for the MGM API (see <xref linkend="ndb-mgm-error"/>) and
- <literal>NDB</literal> API (see
- <xref linkend="ndb-error-messages"/>). Also provided in this
- chapter is a listing of exit codes and messages returned by a
- failed <command>ndbd</command> process, in
+ NDB API (see <xref linkend="ndb-error-messages"/>). Also provided
+ in this chapter is a listing of exit codes and messages returned
+ by a failed <command>ndbd</command> process, in
<xref linkend="ndb-error-messages"/>.
</para>
@@ -307,25 +306,24 @@
<section id="ndb-error-messages">
- <title><literal>NDB</literal> API Errors and Error Handling</title>
+ <title>NDB API Errors and Error Handling</title>
<abstract>
<para>
- This section contains a discussion of error handling in
- <literal>NDB</literal> API applications as well as listing
- listings of the most common <literal>NDB</literal> error codes
- and messages, along with their classifications and likely causes
- for which they might be raised.
+ This section contains a discussion of error handling in NDB API
+ applications as well as listing listings of the most common
+ <literal>NDB</literal> error codes and messages, along with
+ their classifications and likely causes for which they might be
+ raised.
</para>
</abstract>
<para>
For information about the <literal>NdbError</literal> structure,
- which is used to convey error information to
- <literal>NDB</literal> API applications, see
- <xref linkend="struct-ndberror"/>.
+ which is used to convey error information to NDB API applications,
+ see <xref linkend="struct-ndberror"/>.
</para>
<important>
@@ -350,13 +348,13 @@
<section id="ndb-errors-handling">
- <title>Handling <literal>NDB</literal> API Errors</title>
+ <title>Handling NDB API Errors</title>
<abstract>
<para>
- This section describes how <literal>NDB</literal> API errors
- can be detected and mapped onto particular operations.
+ This section describes how NDB API errors can be detected and
+ mapped onto particular operations.
</para>
</abstract>
@@ -407,11 +405,10 @@
<important>
<para>
- If you have worked with older versions of the
- <literal>NDB</literal> API, you should be aware that,
- beginning with MySQL Cluster NDB 6.2.0, the
- <literal>AbortOption</literal> type is a member of
- <literal>NdbOperation</literal>. See
+ If you have worked with older versions of the NDB API, you
+ should be aware that, beginning with MySQL Cluster NDB
+ 6.2.0, the <literal>AbortOption</literal> type is a member
+ of <literal>NdbOperation</literal>. See
<xref linkend="class-ndboperation-abortoption"/>, for more
information.
</para>
@@ -824,18 +821,16 @@
</formalpara>
<para>
- For information about <literal>NDB</literal> API error
- classification and status codes, see
- <xref linkend="ndb-error-classifications"/>. While you should
- not not rely on a specific error code or message text in your
- <literal>NDB</literal> API applications — since error
- codes and messages are both subject to change over time —
- it can be useful to check error codes and messages to help
- determine why a particular failure occurred. For more
- information about these, see <xref linkend="ndb-error-codes"/>.
- For more about <literal>NdbError</literal> and the types of
- information which can be obtained from
- <literal>NdbError</literal> objects, see
+ For information about NDB API error classification and status
+ codes, see <xref linkend="ndb-error-classifications"/>. While
+ you should not not rely on a specific error code or message text
+ in your NDB API applications — since error codes and
+ messages are both subject to change over time — it can be
+ useful to check error codes and messages to help determine why a
+ particular failure occurred. For more information about these,
+ see <xref linkend="ndb-error-codes"/>. For more about
+ <literal>NdbError</literal> and the types of information which
+ can be obtained from <literal>NdbError</literal> objects, see
<xref linkend="struct-ndberror"/>.
</para>
Modified: trunk/ndbapi/ndb-examples.xml
===================================================================
--- trunk/ndbapi/ndb-examples.xml 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/ndbapi/ndb-examples.xml 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 5, Lines Added: 20, Lines Deleted: 25; 3149 bytes
@@ -1,26 +1,22 @@
<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
<!ENTITY % all.entities SYSTEM "all-entities.ent">
%all.entities;
]>
-<chapter id="ndb-examples">
+<section id="ndb-examples">
<title>Practical Examples</title>
- <abstract>
+ <para>
+ This section provides code examples illustrating how to accomplish
+ some basic tasks using the NDB API.
+ </para>
- <para>
- This section provides code examples illustrating how to accomplish
- some basic tasks using the NDB API.
- </para>
+ <para>
+ All of these examples can be compiled and run as provided, and
+ produce sample output to demonstrate their effects.
+ </para>
- <para>
- All of these examples can be compiled and run as provided, and
- produce sample output to demonstrate their effects.
- </para>
-
- </abstract>
-
<section id="ndb-examples-synchronous-transactions">
<title>Using Synchronous Transactions</title>
@@ -2387,9 +2383,9 @@
<abstract>
<para>
- This program illustrates how to use secondary indexes in the
- <literal>NDB</literal> API with the aid of the NdbRecord
- interface introduced in MySQL-5.1.18-6.2.3..
+ This program illustrates how to use secondary indexes in the NDB
+ API with the aid of the NdbRecord interface introduced in
+ MySQL-5.1.18-6.2.3..
</para>
<para>
@@ -2735,7 +2731,7 @@
<section id="ndb-examples-event-handling">
- <title><literal>NDB</literal> API Event Handling Example</title>
+ <title>NDB API Event Handling Example</title>
<indexterm>
<primary>events</primary>
@@ -3863,12 +3859,11 @@
<para>
This example illustrates the manipulation of a
- <literal>BLOB</literal> column in the <literal>NDB</literal> API
- using the <literal>NdbRecord</literal> interface available
- beginning with MySQL Cluster NDB 6.2.3. It demonstrates how to
- perform insert, read, and update operations, using both inline
- value buffers as well as read and write methods. It can be found
- in the file
+ <literal>BLOB</literal> column in the NDB API using the
+ <literal>NdbRecord</literal> interface available beginning with
+ MySQL Cluster NDB 6.2.3. It demonstrates how to perform insert,
+ read, and update operations, using both inline value buffers as
+ well as read and write methods. It can be found in the file
<filename>storage/ndb/ndbapi-examples/ndbapi_blob_ndbrecord/main.cpp</filename>
in the <literal>mysql-5.1-telco</literal> and
<literal>mysql-5.1-telco-6.2</literal> source trees.
@@ -4410,4 +4405,4 @@
</section>
-</chapter>
+</section>
Modified: trunk/ndbapi/ndb-hierarchy.xml
===================================================================
--- trunk/ndbapi/ndb-hierarchy.xml 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/ndbapi/ndb-hierarchy.xml 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 2, Lines Added: 6, Lines Deleted: 6; 1137 bytes
@@ -1,15 +1,15 @@
<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
<!ENTITY % all.entities SYSTEM "all-entities.ent">
%all.entities;
]>
-<chapter id="ndb-hierarchy">
+<section id="ndb-hierarchy">
- <title>The <literal>NDB</literal> Object Hierarachy</title>
+ <title>The NDB API Object Hierarachy</title>
<para>
- Here we provide a hierarchical listing of all classes, interfaces,
- and structures exposed by the <literal>NDB</literal> API.
+ This section provides a hierarchical listing of all classes,
+ interfaces, and structures exposed by the NDB API.
</para>
<para>
@@ -226,4 +226,4 @@
</itemizedlist>
</para>
-</chapter>
+</section>
Modified: trunk/ndbapi/ndb-internals.xml
===================================================================
--- trunk/ndbapi/ndb-internals.xml 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/ndbapi/ndb-internals.xml 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 2, Lines Added: 3, Lines Deleted: 2; 913 bytes
@@ -6,12 +6,13 @@
<chapter id="ndb-internals">
<title>MySQL Cluster Internals</title>
-
+<abstract>
<para>
This chapter contains information about MySQL Cluster that is not
strictly necessary for running the Cluster product, but can prove
useful for development and debugging purposes.
</para>
+</abstract>
<section id="ndb-internals-filesystems">
@@ -3402,7 +3403,7 @@
<listitem>
<formalpara>
- <title>Relation to <literal>NDB</literal> API</title>
+ <title>Relation to NDB API</title>
<para>
It is possible to match the output of <literal>DUMP
Modified: trunk/ndbapi/ndbapi.xml
===================================================================
--- trunk/ndbapi/ndbapi.xml 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/ndbapi/ndbapi.xml 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 2, Lines Added: 40, Lines Deleted: 18; 3633 bytes
@@ -24,21 +24,27 @@
</para>
<para>
- Provides information for developers wishing to use the low-level
- C/C++-language NDB API for the MySQL®
- <literal>NDBCLUSTER</literal> storage engine. Includes concepts,
- terminology, programming class and structure references,
- practical examples, common problems, and tips for using the NDB
- API in applications.
+ This guide provides information for developers wishing to use:
+ The low-level C/C++-language NDB API for the MySQL
+ <literal>NDBCLUSTER</literal> storage engine, the C-language MGM
+ API for communicating with and controlling MySQL Cluster
+ management servers, and other APIs used with MySQL in the
+ context of MySQL Cluster. This Guide includes concepts,
+ terminology, class and function references, practical examples,
+ common problems, and tips for using these APIs in applications.
+ It also contains information about NDB internals that may be of
+ interest to developers working with
+ <literal>NDBCLUSTER</literal>, such as communication protocols
+ employed between nodes, filesystems used by data nodes, and
+ error messages.
</para>
<para>
- The NDB and MGM APIs as presented in this guide are current for
- MySQL 5.1 — note that there have been significant changes
- in the API as implemented in previous MySQL Cluster versions.
- The definitions of NDB API classes and MGM API functions reflect
- the state of the MySQL main development tree as of MySQL 5.1.12
- and later.
+ The information presented in this guide is current for recent
+ MySQL Cluster NDB 6.2, 6.3, and 6.4 releases. You should be
+ aware that there have been significant changes in the NDB API,
+ MGM API, and other particulars in MySQL Cluster versions since
+ MySQL 5.1.12.
</para>
</abstract>
@@ -49,18 +55,34 @@
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="overview.xml"/>
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="getting-started.xml"/>
+ <chapter id="ndbapi">
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="ndb-hierarchy.xml"/>
+ <title>The NDB API</title>
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="ndb-classes.xml"/>
+ <abstract>
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="ndb-errors.xml"/>
+ <para>
+ This chapter contains information about the NDB API, which is
+ used to write applications that access data in the
+ <literal>NDBCLUSTER</literal> storage engine.
+ </para>
+ </abstract>
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="getting-started.xml"/>
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="ndb-hierarchy.xml"/>
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="ndb-classes.xml"/>
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="ndb-examples.xml"/>
+
+ </chapter>
+
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="mgm-api.xml"/>
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="ndb-errors.xml"/>
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="ndb-examples.xml"/>
-
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="ndb-internals.xml"/>
<index/>
Modified: trunk/refman-5.1/Makefile.depends
===================================================================
--- trunk/refman-5.1/Makefile.depends 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/refman-5.1/Makefile.depends 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 7, Lines Added: 7, Lines Deleted: 0; 2303 bytes
@@ -1337,6 +1337,7 @@
dynxml_local_se_archive_INCLUDES = \
../common/fixedchars.ent \
../common/phrases.ent \
+ ../dynamic-docs/storage-engines/engines.xml \
../refman-common/urls.ent \
all-entities.ent \
se-archive-core.xml \
@@ -1361,6 +1362,7 @@
../common/phrases.ent \
../dynamic-docs/command-optvars/mysqld.xml \
../dynamic-docs/metadata-titles.en.xml \
+ ../dynamic-docs/storage-engines/engines.xml \
../refman-common/urls.ent \
all-entities.ent \
se-innodb-core.xml \
@@ -1390,6 +1392,7 @@
dynxml_local_se_memory_INCLUDES = \
../common/fixedchars.ent \
../common/phrases.ent \
+ ../dynamic-docs/storage-engines/engines.xml \
../refman-common/urls.ent \
all-entities.ent \
se-memory-core.xml \
@@ -1414,6 +1417,7 @@
../common/phrases.ent \
../dynamic-docs/command-optvars/mysqld.xml \
../dynamic-docs/metadata-titles.en.xml \
+ ../dynamic-docs/storage-engines/engines.xml \
../refman-common/urls.ent \
all-entities.ent \
se-myisam-core.xml \
@@ -1446,6 +1450,7 @@
../common/phrases.ent \
../dynamic-docs/command-optvars/mysqld.xml \
../dynamic-docs/metadata-titles.en.xml \
+ ../dynamic-docs/storage-engines/engines.xml \
../refman-common/images/published/PSEArch.png \
../refman-common/images/published/blackhole-1.png \
../refman-common/images/published/se-federated-structure.png \
@@ -1973,6 +1978,7 @@
../dynamic-docs/reserved-words/mysql-5.1.6-alpha \
../dynamic-docs/reserved-words/mysql-5.1.7-beta \
../dynamic-docs/reserved-words/mysql-5.1.9-beta \
+ ../dynamic-docs/storage-engines/engines.xml \
../mysql-monitor-2.0/../common/fixedchars.ent \
../mysql-monitor-2.0/../common/phrases.ent \
../mysql-monitor-2.0/../dynamic-docs/faq/monitor.xml \
@@ -2721,6 +2727,7 @@
../dynamic-docs/reserved-words/mysql-5.1.6-alpha \
../dynamic-docs/reserved-words/mysql-5.1.7-beta \
../dynamic-docs/reserved-words/mysql-5.1.9-beta \
+ ../dynamic-docs/storage-engines/engines.xml \
../dynamic-docs/topic-quickref/quickrefs.xml \
../mysql-monitor-2.0/../common/fixedchars.ent \
../mysql-monitor-2.0/../common/phrases.ent \
Modified: trunk/refman-5.1-maria/Makefile.depends
===================================================================
--- trunk/refman-5.1-maria/Makefile.depends 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/refman-5.1-maria/Makefile.depends 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 0; 1160 bytes
@@ -438,6 +438,7 @@
../refman-5.1/../dynamic-docs/reserved-words/mysql-5.1.6-alpha \
../refman-5.1/../dynamic-docs/reserved-words/mysql-5.1.7-beta \
../refman-5.1/../dynamic-docs/reserved-words/mysql-5.1.9-beta \
+ ../refman-5.1/../dynamic-docs/storage-engines/engines.xml \
../refman-5.1/../refman-common/../common/fixedchars.ent \
../refman-5.1/../refman-common/../common/phrases.ent \
../refman-5.1/../refman-common/../refman-common/apis-php-mysql.xml \
@@ -1010,6 +1011,7 @@
../refman-5.1/../common/phrases.ent \
../refman-5.1/../dynamic-docs/command-optvars/mysqld.xml \
../refman-5.1/../dynamic-docs/metadata-titles.en.xml \
+ ../refman-5.1/../dynamic-docs/storage-engines/engines.xml \
../refman-5.1/../refman-common/images/published/blackhole-1.png \
../refman-5.1/../refman-common/images/published/se-federated-structure.png \
../refman-5.1/../refman-common/urls.ent \
Modified: trunk/refman-6.0/Makefile.depends
===================================================================
--- trunk/refman-6.0/Makefile.depends 2009-01-23 03:27:40 UTC (rev 13359)
+++ trunk/refman-6.0/Makefile.depends 2009-01-23 11:23:15 UTC (rev 13360)
Changed blocks: 8, Lines Added: 8, Lines Deleted: 0; 2510 bytes
@@ -1132,6 +1132,7 @@
dynxml_local_se_archive_INCLUDES = \
../common/fixedchars.ent \
../common/phrases.ent \
+ ../dynamic-docs/storage-engines/engines.xml \
../refman-common/urls.ent \
all-entities.ent \
se-archive-core.xml \
@@ -1156,6 +1157,7 @@
../common/phrases.ent \
../dynamic-docs/command-optvars/mysqld.xml \
../dynamic-docs/metadata-titles.en.xml \
+ ../dynamic-docs/storage-engines/engines.xml \
../refman-common/urls.ent \
all-entities.ent \
se-falcon-core.xml \
@@ -1181,6 +1183,7 @@
../common/phrases.ent \
../dynamic-docs/command-optvars/mysqld.xml \
../dynamic-docs/metadata-titles.en.xml \
+ ../dynamic-docs/storage-engines/engines.xml \
../refman-common/urls.ent \
all-entities.ent \
se-innodb-core.xml \
@@ -1235,6 +1238,7 @@
dynxml_local_se_memory_INCLUDES = \
../common/fixedchars.ent \
../common/phrases.ent \
+ ../dynamic-docs/storage-engines/engines.xml \
../refman-common/urls.ent \
all-entities.ent \
se-memory-core.xml \
@@ -1259,6 +1263,7 @@
../common/phrases.ent \
../dynamic-docs/command-optvars/mysqld.xml \
../dynamic-docs/metadata-titles.en.xml \
+ ../dynamic-docs/storage-engines/engines.xml \
../refman-common/urls.ent \
all-entities.ent \
se-myisam-core.xml \
@@ -1292,6 +1297,7 @@
../dynamic-docs/command-optvars/mysqld.xml \
../dynamic-docs/faq/se-maria.xml \
../dynamic-docs/metadata-titles.en.xml \
+ ../dynamic-docs/storage-engines/engines.xml \
../refman-common/images/published/PSEArch.png \
../refman-common/images/published/blackhole-1.png \
../refman-common/images/published/se-federated-structure.png \
@@ -1737,6 +1743,7 @@
../dynamic-docs/faq/se-maria.xml \
../dynamic-docs/metadata-titles.en.xml \
../dynamic-docs/opsfunctions/opfunctions.xml \
+ ../dynamic-docs/storage-engines/engines.xml \
../mysql-monitor-2.0/../common/fixedchars.ent \
../mysql-monitor-2.0/../common/phrases.ent \
../mysql-monitor-2.0/../dynamic-docs/faq/monitor.xml \
@@ -2347,6 +2354,7 @@
../dynamic-docs/faq/se-maria.xml \
../dynamic-docs/metadata-titles.en.xml \
../dynamic-docs/opsfunctions/opfunctions.xml \
+ ../dynamic-docs/storage-engines/engines.xml \
../dynamic-docs/topic-quickref/quickrefs.xml \
../mysql-monitor-2.0/../common/fixedchars.ent \
../mysql-monitor-2.0/../common/phrases.ent \
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r13360 - in trunk: mysql-monitor-2.0 mysqlqb ndbapi refman-5.1 refman-5.1-maria refman-6.0 | jon | 23 Jan |
