Author: jstephens
Date: 2006-09-02 09:29:13 +0200 (Sat, 02 Sep 2006)
New Revision: 3206
Log:
Reformat
Modified:
trunk/ndbapi/mgm-api.xml
trunk/refman-5.0/news-5.0.xml
trunk/refman-5.1/news-5.1.xml
trunk/refman-5.1/partitioning.xml
trunk/refman-5.1/sql-syntax.xml
Modified: trunk/ndbapi/mgm-api.xml
===================================================================
--- trunk/ndbapi/mgm-api.xml 2006-09-02 06:45:22 UTC (rev 3205)
+++ trunk/ndbapi/mgm-api.xml 2006-09-02 07:29:13 UTC (rev 3206)
Changed blocks: 3, Lines Added: 2, Lines Deleted: 8; 701 bytes
@@ -520,9 +520,8 @@
</section>
+ <section id="ndb-logevent-get-fd">
- <section id="ndb-logevent-get-fd">
-
<title><literal>ndb_logevent_get_fd()</literal></title>
<indexterm>
@@ -584,8 +583,6 @@
</formalpara>
-
-
<!--
<formalpara>
@@ -600,11 +597,8 @@
</formalpara>
-->
+ </section>
-
- </section>
-
-
<section id="ndb-logevent-get-next">
<title><literal>ndb_logevent_get_next()</literal></title>
Modified: trunk/refman-5.0/news-5.0.xml
===================================================================
--- trunk/refman-5.0/news-5.0.xml 2006-09-02 06:45:22 UTC (rev 3205)
+++ trunk/refman-5.0/news-5.0.xml 2006-09-02 07:29:13 UTC (rev 3206)
Changed blocks: 5, Lines Added: 8, Lines Deleted: 7; 1511 bytes
@@ -874,13 +874,14 @@
t5 NATURAL JOIN t6
)
ON (t3.id3 = t2.id3 AND t5.id5 = t2.id5)
- );</programlisting>
+);
+</programlisting>
<para>
(Bug #21007)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal> (Direct APIs): Invoking the MGM
@@ -888,7 +889,7 @@
a memory leak. (Bug #21671)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal> (Direct APIs): The MGM API
@@ -896,12 +897,12 @@
actually implemented. (Bug #21129)
</para>
</listitem>
-
+
<listitem>
<para>
A memory leak was found when running
<literal><command>ndb_mgm</command> -e "SHOW"</literal>. (Bug
- #21670)
+ #21670)
</para>
</listitem>
@@ -914,7 +915,7 @@
circumstances. (Bug #21017, Bug #21050)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: An issue that arose from a
@@ -922,7 +923,7 @@
<xref linkend="news-5-0-23"/>.)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: The management client
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2006-09-02 06:45:22 UTC (rev 3205)
+++ trunk/refman-5.1/news-5.1.xml 2006-09-02 07:29:13 UTC (rev 3206)
Changed blocks: 6, Lines Added: 30, Lines Deleted: 29; 4972 bytes
@@ -628,48 +628,49 @@
REPAIR TABLE <replaceable>tbl_name</replaceable> QUICK;
</programlisting>
</listitem>
-
+
<listitem>
<para>
The server's handling of the number of partitions or
- subpartitions specified in a <literal>PARTITIONS</literal>
- or <literal>SUBPARTITIONS</literal> clause was changed.
- Beginning with this release, the number of partitions must:
+ subpartitions specified in a <literal>PARTITIONS</literal> or
+ <literal>SUBPARTITIONS</literal> clause was changed. Beginning
+ with this release, the number of partitions must:
</para>
-
+
<itemizedlist>
+
<listitem>
<para>
be a positive, non-zero integer
</para>
</listitem>
-
+
<listitem>
<para>
not have any leading zeroes
</para>
</listitem>
-
+
<listitem>
<para>
not be an expression
</para>
</listitem>
+
</itemizedlist>
-
+
<para>
Also beginning with this version, no attempt is made to
convert, truncate, or evaluate a <literal>PARTITIONS</literal>
or <literal>SUBPARTITIONS</literal> value; instead, the
<literal>CREATE TABLE</literal> or <literal>ALTER
- TABLE</literal> statement containing the
+ TABLE</literal> statement containing the
<literal>PARTITIONS</literal> or
<literal>SUBPARTITIONS</literal> clause now fails with an
- appropriate error message. (Bug #15890)
+ appropriate error message. (Bug #15890)
</para>
-
</listitem>
-
+
<listitem>
<para>
A misleading error message was displayed when attempting to
@@ -677,25 +678,25 @@
table. (Bug #21862)
</para>
</listitem>
-
+
<listitem>
<para>
Errors could be generated during the execution of certain
prepared statements that ran queries on partitioned tables.
- (Bug #21658)
+ (Bug #21658)
</para>
</listitem>
-
+
<listitem>
<para>
Using relative paths for <literal>DATA DIRECTORY</literal> or
<literal>INDEX DIRECTORY</literal> with a partitioned table
- generated a warning rather than an error, and caused
+ generated a warning rather than an error, and caused
<quote>junk</quote> files to be created in the server's data
directory. (Bug #21350)
</para>
</listitem>
-
+
<listitem>
<para>
Using <literal>EXPLAIN PARTITIONS</literal> with a query on a
@@ -704,7 +705,7 @@
server to crash. (Bug #21339)
</para>
</listitem>
-
+
<listitem>
<para>
Running <literal>SHOW TABLE STATUS</literal> on any
@@ -714,17 +715,17 @@
rather with <literal>AUTO_INCREMENT</literal> handling in the
partitioning code — however, the table did not have to
have an <literal>AUTO_INCREMENT</literal> column for the bug
- to manifest. (Bug #21173)
+ to manifest. (Bug #21173)
</para>
</listitem>
-
+
<listitem>
<para>
Some <literal>ALTER TABLE</literal> statements affecting a
table's subpartitioning could hang. (Bug #21143)
</para>
</listitem>
-
+
<listitem>
<para>
Scheduled events that invoked stored procedures executing DDL
@@ -2024,15 +2025,15 @@
could cause errors or crash the server. (Bug #20583)
</para>
</listitem>
-
+
<listitem>
<para>
- <literal>NDB Cluster</literal> (Direct APIss): Invoking the MGM
- API function <literal>ndb_mgm_listen_event()</literal> caused
- a memory leak. (Bug #21671)
+ <literal>NDB Cluster</literal> (Direct APIss): Invoking the
+ MGM API function <literal>ndb_mgm_listen_event()</literal>
+ caused a memory leak. (Bug #21671)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: The management client
@@ -2076,15 +2077,15 @@
cluster log for each cluster node. (Bug #21044)
</para>
</listitem>
-
+
<listitem>
<para>
A memory leak was found when running
<literal><command>ndb_mgm</command> -e "SHOW"</literal>. (Bug
- #21670)
+ #21670)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal> (Direct APIs): The MGM API
Modified: trunk/refman-5.1/partitioning.xml
===================================================================
--- trunk/refman-5.1/partitioning.xml 2006-09-02 06:45:22 UTC (rev 3205)
+++ trunk/refman-5.1/partitioning.xml 2006-09-02 07:29:13 UTC (rev 3206)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 527 bytes
@@ -666,7 +666,7 @@
partition names <literal>mypart</literal> and
<literal>MyPart</literal>.
</para>
-
+
<para>
When you specify the number of partitions for the table, this must
be expressed as a positive, non-zero integer literal with no
Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml 2006-09-02 06:45:22 UTC (rev 3205)
+++ trunk/refman-5.1/sql-syntax.xml 2006-09-02 07:29:13 UTC (rev 3206)
Changed blocks: 3, Lines Added: 30, Lines Deleted: 29; 2932 bytes
@@ -895,10 +895,10 @@
primary key) that the table might have, and the column or
columns used in the partitioning expression, as discussed in
<link linkend="partitioning-limitations-partitioning-keys-unique-keys">Partitioning
- Limitations: Partitioning Keys and Unique Keys</link>. The
- <literal>CREATE TABLE ... PARTITION BY</literal> rules for specifying the
- number of partitions also apply to <literal>ALTER
- TABLE ... PARTITION BY</literal>.
+ Limitations: Partitioning Keys and Unique Keys</link>. The
+ <literal>CREATE TABLE ... PARTITION BY</literal> rules for
+ specifying the number of partitions also apply to
+ <literal>ALTER TABLE ... PARTITION BY</literal>.
</para>
<para>
@@ -3532,7 +3532,7 @@
integer value.
</para>
</listitem>
-
+
<listitem>
<para>
MySQL 5.1.12 introduces rigourous checking of the value used
@@ -3540,31 +3540,32 @@
<literal>SUBPARTITIONS</literal> clause. Beginning with this
version, this value must adhere to the following rules:
</para>
-
- <itemizedlist>
- <listitem>
- <para>
- The value must be a positive, non-zero integer.
- </para>
- </listitem>
-
- <listitem>
- <para>
- No leading zeroes are permitted.
- </para>
- </listitem>
-
- <listitem>
- <para>
- The value must be an integer literal, and cannot not be an
- expression. For example, <literal>PARTITIONS
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ The value must be a positive, non-zero integer.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ No leading zeroes are permitted.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The value must be an integer literal, and cannot not be
+ an expression. For example, <literal>PARTITIONS
0.2E+01</literal> is not allowed, even though
- <literal>0.2E+01</literal> evaluates to
- <literal>2</literal>. (Bug #15890)
- </para>
- </listitem>
- </itemizedlist>
-
+ <literal>0.2E+01</literal> evaluates to
+ <literal>2</literal>. (Bug #15890)
+ </para>
+ </listitem>
+
+ </itemizedlist>
</listitem>
</itemizedlist>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r3206 - in trunk: ndbapi refman-5.0 refman-5.1 | jon | 2 Sep |
