List:Commits« Previous MessageNext Message »
From:jon Date:December 12 2008 12:04am
Subject:svn commit - mysqldoc@docsrva: r12928 - in trunk: dynamic-docs/changelog mysql-monitor-2.0 refman-5.1 refman-5.1-maria refman-6.0 topic-guides/topics-...
View as plain text  
Author: jstephens
Date: 2008-12-12 01:04:07 +0100 (Fri, 12 Dec 2008)
New Revision: 12928

Log:

Fixed table/partitioning maintenance statement mess (or so we can hope)

Rebuilt dependencies



Modified:
   trunk/dynamic-docs/changelog/mysqld-1.xml
   trunk/mysql-monitor-2.0/Makefile.depends
   trunk/refman-5.1-maria/Makefile.depends
   trunk/refman-5.1/partitioning.xml
   trunk/refman-5.1/sql-syntax-data-definition.xml
   trunk/refman-5.1/sql-syntax-server-administration.xml
   trunk/refman-6.0/partitioning.xml
   trunk/refman-6.0/sql-syntax-data-definition.xml
   trunk/refman-6.0/sql-syntax-server-administration.xml
   trunk/topic-guides/topics-5.1/Makefile.depends
   trunk/topic-guides/topics-6.0/Makefile.depends


Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml	2008-12-12 00:01:47 UTC (rev 12927)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml	2008-12-12 00:04:07 UTC (rev 12928)
Changed blocks: 3, Lines Added: 37, Lines Deleted: 13; 2353 bytes

@@ -8274,7 +8274,7 @@
 
       <para>
         The following statements did not function correctly with
-        corrupted or crashed tables and have been removed:
+        corrupted or crashed tables and have been disabled:
       </para>
 
       <itemizedlist>

@@ -8331,12 +8331,8 @@
     <message ver="5.1.27">
 
       <para>
-        This restores functionality missing since the removal of
-        <literal>ALTER TABLE ... ANALYZE PARTITION</literal>,
-        <literal>ALTER TABLE ... CHECK PARTITION</literal>,
-        <literal>ALTER TABLE ... OPTIMIZE PARTITION</literal>, and
-        <literal>ALTER TABLE ... REPAIR PARTITION</literal> in MySQL
-        5.1.24.
+        Also as a result of this fix, the following statements which
+        were disabled in MySQL 5.1.24 have been re-enabled:
       </para>
 
     </message>

@@ -8344,16 +8340,44 @@
     <message ver="6.0.6">
 
       <para>
-        This restores functionality missing since the removal of
-        <literal>ALTER TABLE ... ANALYZE PARTITION</literal>,
-        <literal>ALTER TABLE ... CHECK PARTITION</literal>,
-        <literal>ALTER TABLE ... OPTIMIZE PARTITION</literal>, and
-        <literal>ALTER TABLE ... REPAIR PARTITION</literal> in MySQL
-        6.0.5.
+        Also as a result of this fix, the following statements which
+        were disabled in MySQL 6.0.5 have been re-enabled:
       </para>
 
     </message>
 
+    <message ver="5.1.27,6.0.6">
+
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            <literal>ALTER TABLE ... ANALYZE PARTITION</literal>
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <literal>ALTER TABLE ... CHECK PARTITION</literal>
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <literal>ALTER TABLE ... OPTIMIZE PARTITION</literal>
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <literal>ALTER TABLE ... REPAIR PARTITION</literal>
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
+    </message>
+
   </logentry>
 
   <logentry entrytype="bug">


Modified: trunk/mysql-monitor-2.0/Makefile.depends
===================================================================
--- trunk/mysql-monitor-2.0/Makefile.depends	2008-12-12 00:01:47 UTC (rev 12927)
+++ trunk/mysql-monitor-2.0/Makefile.depends	2008-12-12 00:04:07 UTC (rev 12928)
Changed blocks: 2, Lines Added: 4, Lines Deleted: 2; 1190 bytes

@@ -245,7 +245,8 @@
 	images/published/monitor-migration-confirm.png \
 	images/published/monitor-migration-progress.png
 deployment_SOURCES = deployment.xml $(deployment_INCLUDES)
-deployment_IDMAPS =
+deployment_IDMAPS = \
+	../mysql-monitor-2.0/metadata/dashboard-configure.idmap
 deployment.validpure: $(deployment_SOURCES)
 deployment.titles: $(deployment_SOURCES)
 deployment.useless: $(deployment_SOURCES)

@@ -264,7 +265,8 @@
 	version.ent
 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 =
+dynxml_local_monitor_faq_IDMAPS = \
+	../mysql-monitor-2.0/metadata/dashboard-query-analysis.idmap
 dynxml-local-monitor-faq.validpure: $(dynxml_local_monitor_faq_SOURCES)
 dynxml-local-monitor-faq.titles: $(dynxml_local_monitor_faq_SOURCES)
 dynxml-local-monitor-faq.useless: $(dynxml_local_monitor_faq_SOURCES)


Modified: trunk/refman-5.1/partitioning.xml
===================================================================
--- trunk/refman-5.1/partitioning.xml	2008-12-12 00:01:47 UTC (rev 12927)
+++ trunk/refman-5.1/partitioning.xml	2008-12-12 00:04:07 UTC (rev 12928)
Changed blocks: 1, Lines Added: 183, Lines Deleted: 30; 7924 bytes

@@ -3534,60 +3534,213 @@
         <secondary>repairing</secondary>
       </indexterm>
 
+      <indexterm>
+        <primary>ANALYZE TABLE</primary>
+        <secondary>and partitioning</secondary>
+      </indexterm>
+
+      <indexterm>
+        <primary>CHECK TABLE</primary>
+        <secondary>and partitioning</secondary>
+      </indexterm>
+
+      <indexterm>
+        <primary>OPTIMIZE TABLE</primary>
+        <secondary>and partitioning</secondary>
+      </indexterm>
+
+      <indexterm>
+        <primary>REPAIR TABLE</primary>
+        <secondary>and partitioning</secondary>
+      </indexterm>
+
       <para>
-        Beginning with MySQL 5.1.27, MySQL &current-series; supports the
-        statements <literal role="stmt">CHECK TABLE</literal>,
+        A number of table and partition maintenance tasks can be carried
+        out using SQL statements intended for such purposes on
+        partitioned tables in MySQL &current-series;.
+      </para>
+
+      <para>
+        Table maintenance of partitioned tables can be accomplished
+        using the statements <literal role="stmt">CHECK TABLE</literal>,
         <literal role="stmt">OPTIMIZE TABLE</literal>,
         <literal role="stmt">ANALYZE TABLE</literal>, and
-        <literal role="stmt">REPAIR TABLE</literal> for partitioned
-        tables.
+        <literal role="stmt">REPAIR TABLE</literal>, which are supported
+        for partitioned tables as of MySQL 5.1.27.
       </para>
 
       <para>
-        Beginning with MySQL 5.1.5, you can also rebuild partitions
-        using <literal>ALTER TABLE ... REBUILD PARTITION</literal>,
-        which has the same effect as dropping all records stored in the
-        partition, then reinserting them. This can be useful for
-        purposes of defragmentation. You can rebuild a one or more
-        partitions belonging to the same table at one time using this
-        statement, as shown in these examples:
+        Also beginning with MySQL 5.1.27, you can use a number of
+        extensions to <literal role="stmt">ALTER TABLE</literal> for
+        performing operations of this type on one or more partitions
+        directly, as described in the following list:
+      </para>
 
+      <itemizedlist>
+
+        <listitem>
+          <formalpara>
+
+            <title>Rebuilding partitions</title>
+
+            <para>
+              Rebuilds the partition; this has the same effect as
+              dropping all records stored in the partition, then
+              reinserting them. This can be useful for purposes of
+              defragmentation.
+            </para>
+
+          </formalpara>
+
+          <para>
+            Example:
+          </para>
+
 <programlisting>
-ALTER TABLE t1 REBUILD PARTITION p1;
-ALTER TABLE t1 REBUILD PARTITION p0, p2;
+ALTER TABLE t1 REBUILD PARTITION p0, p1;
 </programlisting>
+        </listitem>
 
-        Executing the first statement rebuilds the partition named
-        <literal>p1</literal> from the table <literal>t1</literal>.
-        Performing the second statement rebuilds partitions
-        <literal>p0</literal> and <literal>p2</literal> from table
-        <literal>t1</literal>.
-      </para>
+        <listitem>
+          <formalpara>
 
-      <para>
-        <literal>ALTER TABLE ... REORGANIZE PARTITION</literal> also
-        causes partition files to be rebuilt.
-      </para>
+            <title>Optimizing partitions</title>
 
+            <para>
+              If you have deleted a large number of rows from a
+              partition or if you have made many changes to a
+              partitioned table with variable-length rows (that is,
+              having <literal>VARCHAR</literal>,
+              <literal>BLOB</literal>, or <literal>TEXT</literal>
+              columns), you can use <literal>ALTER TABLE ... OPTIMIZE
+              PARTITION</literal> to reclaim any unused space and to
+              defragment the partition data file.
+            </para>
+
+          </formalpara>
+
+          <para>
+            Example:
+          </para>
+
+<programlisting>
+ALTER TABLE t1 OPTIMIZE PARTITION p0, p1;
+</programlisting>
+
+          <para>
+            Using <literal>OPTIMIZE PARTITION</literal> on a given
+            partition is equivalent to running <literal>CHECK
+            PARTITION</literal>, <literal>ANALYZE PARTITION</literal>,
+            and <literal>REPAIR PARTITION</literal> on that partition.
+          </para>
+        </listitem>
+
+        <listitem>
+          <formalpara>
+
+            <title>Analyzing partitions</title>
+
+            <para>
+              This reads and stores the key distributions for
+              partitions.
+            </para>
+
+          </formalpara>
+
+          <para>
+            Example:
+          </para>
+
+<programlisting>
+ALTER TABLE t1 ANALYZE PARTITION p3;</programlisting>
+        </listitem>
+
+        <listitem>
+          <formalpara>
+
+            <title>Repairing partitions</title>
+
+            <para>
+              This repairs corrupted partitions.
+            </para>
+
+          </formalpara>
+
+          <para>
+            Example:
+          </para>
+
+<programlisting>
+ALTER TABLE t1 REPAIR PARTITION p0,p1;
+</programlisting>
+        </listitem>
+
+        <listitem>
+          <formalpara>
+
+            <title>Checking partitions</title>
+
+            <para>
+              You can check partitions for errors in much the same way
+              that you can use <literal>CHECK TABLE</literal> with
+              non-partitioned tables.
+            </para>
+
+          </formalpara>
+
+          <para>
+            Example:
+          </para>
+
+<programlisting>
+ALTER TABLE trb3 CHECK PARTITION p1;
+</programlisting>
+
+          <para>
+            This command will tell you if the data or indexes in
+            partition <literal>p1</literal> of table
+            <literal>t1</literal> are corrupted. If this is the case,
+            use <literal>ALTER TABLE ... REPAIR PARTITION</literal> to
+            repair the partition.
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
       <note>
         <para>
           The statements <literal>ALTER TABLE ... ANALYZE
           PARTITION</literal>, <literal>ALTER TABLE ... CHECK
           PARTITION</literal>, <literal>ALTER TABLE ... OPTIMIZE
           PARTITION</literal>, and <literal>ALTER TABLE ... REPAIR
-          PARTITION</literal> &mdash; intended to, respectively,
-          analyze, check, optimize, and repair individual or multiple
-          partitions &mdash; were introduced in MySQL 5.1.5 and then
-          removed in MySQL 5.1.24. (Bug #20129)
+          PARTITION</literal> were originally introduced in MySQL 5.1.5,
+          but did not work properly and were disabled in MySQL 5.1.24.
+          They were re-introduced in MySQL 5.1.27. (Bug #20129) The use
+          of these partitioning-specific <literal>ALTER TABLE</literal>
+          statements with tables which are not partitioned is not
+          supported; beginning with MySQL 5.1.31, it is expressly
+          disallowed. (Bug #39434)
         </para>
 
         <para>
-          The use of <command>mysqlcheck</command> or
-          <command>myisamchk</command> is also not supported with
-          partitioned tables.
+          <literal>ALTER TABLE ... REBUILD PARTITION</literal> was also
+          introduced in MySQL 5.1.5.
         </para>
       </note>
 
+      <remark role="NOTE">
+        [js] Commented out following para, pending verification of the
+        statement contained therein.
+      </remark>
+
+<!--
+      <para>
+        The use of <command>mysqlcheck</command> and
+        <command>myisamchk</command> is also not supported with
+        partitioned tables.
+      </para>
+-->
+
     </section>
 
     <section id="partitioning-info">


Modified: trunk/refman-5.1/sql-syntax-data-definition.xml
===================================================================
--- trunk/refman-5.1/sql-syntax-data-definition.xml	2008-12-12 00:01:47 UTC (rev 12927)
+++ trunk/refman-5.1/sql-syntax-data-definition.xml	2008-12-12 00:04:07 UTC (rev 12928)
Changed blocks: 2, Lines Added: 18, Lines Deleted: 14; 3236 bytes

@@ -2153,24 +2153,28 @@
           providing partition maintenance and repair functionality
           analogous to that implemented for non-partitioned tables by
           statements such as <literal role="stmt">CHECK TABLE</literal>
-          and <literal role="stmt">REPAIR TABLE</literal> (which are
-          <emphasis>not</emphasis> supported for partitioned tables).
-          These include <literal>ANALYZE PARTITION</literal>,
-          <literal>CHECK PARTITION</literal>, <literal>OPTIMIZE
-          PARTITION</literal>, <literal>REBUILD PARTITION</literal>, and
-          <literal>REPAIR PARTITION</literal>. Each of these options
-          takes a <replaceable>partition_names</replaceable> clause
-          consisting of one or more names of partitions, separated by
-          commas. The partitions must already exist in the table to be
-          altered. For more information and examples, see
+          and <literal role="stmt">REPAIR TABLE</literal> (which are are
+          also supported for partitioned tables, beginning with MySQL
+          5.1.27 &mdash; see note at the end of this item). These
+          include <literal>ANALYZE PARTITION</literal>, <literal>CHECK
+          PARTITION</literal>, <literal>OPTIMIZE PARTITION</literal>,
+          <literal>REBUILD PARTITION</literal>, and <literal>REPAIR
+          PARTITION</literal>. Each of these options takes a
+          <replaceable>partition_names</replaceable> clause consisting
+          of one or more names of partitions, separated by commas. The
+          partitions must already exist in the table to be altered. For
+          more information and examples, see
           <xref linkend="partitioning-maintenance"/>.
         </para>
 
         <para>
           The <literal>ANALYZE PARTITION</literal>, <literal>CHECK
           PARTITION</literal>, <literal>OPTIMIZE PARTITION</literal>,
-          and <literal>REPAIR PARTITION</literal> options were removed
-          in MySQL 5.1.24.
+          and <literal>REPAIR PARTITION</literal> options were disabled
+          in MySQL 5.1.24, and re-enabled in MySQL 5.1.27. (Bug #20129)
+          They are not supported for tables which are not partitioned;
+          beginning with MySQL 5.1.31, they are disallowed for such
+          tables.
         </para>
 
         <note>

@@ -2191,8 +2195,8 @@
           <literal>REMOVE PARTITIONING</literal> was introduced in MySQL
           5.1.8 for the purpose of removing a table's partitioning
           without otherwise affecting the table or its data.
-          (Previously, this was done using the <literal>ENGINE
-          </literal> option.) This option can be combined with other
+          (Previously, this was done using the <literal>ENGINE</literal>
+          option.) This option can be combined with other
           <literal role="stmt">ALTER TABLE</literal> options such as
           those used to add, drop, or rename drop columns or indexes.
         </para>


Modified: trunk/refman-5.1/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.1/sql-syntax-server-administration.xml	2008-12-12 00:01:47 UTC (rev 12927)
+++ trunk/refman-5.1/sql-syntax-server-administration.xml	2008-12-12 00:04:07 UTC (rev 12928)
Changed blocks: 4, Lines Added: 23, Lines Deleted: 12; 3015 bytes

@@ -1818,7 +1818,12 @@
 
       <para>
         Beginning with MySQL 5.1.27, <literal role="stmt">ANALYZE
-        TABLE</literal> is also supported for partitioned tables.
+        TABLE</literal> is also supported for partitioned tables. Also
+        beginning with MySQL 5.1.27, you can use <literal>ALTER TABLE
+        ... ANALYZE PARTITION</literal> to analyze one or more
+        partitions; for more information, see
+        <xref linkend="alter-table"/>, and
+        <xref linkend="partitioning-maintenance"/>.
       </para>
 
       <remark role="help-description-end"/>

@@ -2021,8 +2026,12 @@
       </para>
 
       <para>
-        <literal role="stmt">CHECK TABLE</literal> is not supported for
-        partitioned tables before MySQL 5.1.27.
+        Beginning with MySQL 5.1.27, <literal role="stmt">CHECK
+        TABLE</literal> is also supported for partitioned tables. Also
+        beginning with MySQL 5.1.27, you can use <literal>ALTER TABLE
+        ... CHECK PARTITION</literal> to check one or more partitions;
+        for more information, see <xref linkend="alter-table"/>, and
+        <xref linkend="partitioning-maintenance"/>.
       </para>
 
       <remark role="help-description-end"/>

@@ -2449,10 +2458,12 @@
 
       <para>
         Beginning with MySQL 5.1.27, <literal role="stmt">OPTIMIZE
-        TABLE</literal> is also supported for partitioned tables.
-        Additional statements can also be used for rebuilding partitions
-        &mdash; see <xref linkend="partitioning-maintenance"/>, for
-        information about these.
+        TABLE</literal> is also supported for partitioned tables. Also
+        beginning with MySQL 5.1.27, you can use <literal>ALTER TABLE
+        ... OPTIMIZE PARTITION</literal> to optimize one or more
+        partitions; for more information, see
+        <xref linkend="alter-table"/>, and
+        <xref linkend="partitioning-maintenance"/>.
       </para>
 
       <remark role="help-description-end"/>

@@ -2642,11 +2653,11 @@
 
       <para>
         Beginning with MySQL 5.1.27, <literal role="stmt">REPAIR
-        TABLE</literal> is also supported for partitioned tables.
-        Additional statements exist which can be used for rebuilding
-        partitions &mdash; see
-        <xref linkend="partitioning-maintenance"/>, for information
-        about these.
+        TABLE</literal> is also supported for partitioned tables. Also
+        beginning with MySQL 5.1.27, you can use <literal>ALTER TABLE
+        ... REPAIR PARTITION</literal> to repair one or more partitions;
+        for more information, see <xref linkend="alter-table"/>, and
+        <xref linkend="partitioning-maintenance"/>.
       </para>
 
       <remark role="help-description-end"/>


Modified: trunk/refman-5.1-maria/Makefile.depends
===================================================================
--- trunk/refman-5.1-maria/Makefile.depends	2008-12-12 00:01:47 UTC (rev 12927)
+++ trunk/refman-5.1-maria/Makefile.depends	2008-12-12 00:04:07 UTC (rev 12928)
Changed blocks: 6, Lines Added: 26, Lines Deleted: 0; 3794 bytes

@@ -360,6 +360,9 @@
 	../refman-5.1/../dynamic-docs/reserved-words/mysql-5.0.66a \
 	../refman-5.1/../dynamic-docs/reserved-words/mysql-5.0.67 \
 	../refman-5.1/../dynamic-docs/reserved-words/mysql-5.0.68 \
+	../refman-5.1/../dynamic-docs/reserved-words/mysql-5.0.70 \
+	../refman-5.1/../dynamic-docs/reserved-words/mysql-5.0.72 \
+	../refman-5.1/../dynamic-docs/reserved-words/mysql-5.0.74 \
 	../refman-5.1/../dynamic-docs/reserved-words/mysql-5.0.9-beta \
 	../refman-5.1/../dynamic-docs/reserved-words/mysql-5.1.11-beta \
 	../refman-5.1/../dynamic-docs/reserved-words/mysql-5.1.12-beta \

@@ -379,6 +382,7 @@
 	../refman-5.1/../dynamic-docs/reserved-words/mysql-5.1.28-rc \
 	../refman-5.1/../dynamic-docs/reserved-words/mysql-5.1.29-rc \
 	../refman-5.1/../dynamic-docs/reserved-words/mysql-5.1.3-alpha \
+	../refman-5.1/../dynamic-docs/reserved-words/mysql-5.1.30 \
 	../refman-5.1/../dynamic-docs/reserved-words/mysql-5.1.4-alpha \
 	../refman-5.1/../dynamic-docs/reserved-words/mysql-5.1.5-alpha \
 	../refman-5.1/../dynamic-docs/reserved-words/mysql-5.1.6-alpha \

@@ -505,6 +509,16 @@
 	../refman-5.1/extending-mysql.xml \
 	../refman-5.1/faqs.xml \
 	../refman-5.1/functions-core.xml \
+	../refman-5.1/images/published/mysql-cfg-fig1.png \
+	../refman-5.1/images/published/mysql-cfg-fig10.png \
+	../refman-5.1/images/published/mysql-cfg-fig2.png \
+	../refman-5.1/images/published/mysql-cfg-fig3.png \
+	../refman-5.1/images/published/mysql-cfg-fig4.png \
+	../refman-5.1/images/published/mysql-cfg-fig5.png \
+	../refman-5.1/images/published/mysql-cfg-fig6.png \
+	../refman-5.1/images/published/mysql-cfg-fig7.png \
+	../refman-5.1/images/published/mysql-cfg-fig8.png \
+	../refman-5.1/images/published/mysql-cfg-fig9.png \
 	../refman-5.1/information-schema.xml \
 	../refman-5.1/installing-core.xml \
 	../refman-5.1/internationalization.xml \

@@ -714,6 +728,16 @@
 	../refman-5.1/../refman-common/images/published/scaleout.png \
 	../refman-5.1/../refman-common/images/published/se-federated-structure.png \
 	../refman-5.1/../refman-common/images/published/submaster-performance.png \
+	../refman-5.1/images/published/mysql-cfg-fig1.png \
+	../refman-5.1/images/published/mysql-cfg-fig10.png \
+	../refman-5.1/images/published/mysql-cfg-fig2.png \
+	../refman-5.1/images/published/mysql-cfg-fig3.png \
+	../refman-5.1/images/published/mysql-cfg-fig4.png \
+	../refman-5.1/images/published/mysql-cfg-fig5.png \
+	../refman-5.1/images/published/mysql-cfg-fig6.png \
+	../refman-5.1/images/published/mysql-cfg-fig7.png \
+	../refman-5.1/images/published/mysql-cfg-fig8.png \
+	../refman-5.1/images/published/mysql-cfg-fig9.png \
 	../refman-common/../refman-common/images/published/memcached-flow.png \
 	../refman-common/../refman-common/images/published/memcached-memalloc.png \
 	../refman-common/../refman-common/images/published/memcached-overview.png \

@@ -745,6 +769,7 @@
 	../ndbapi/metadata/mgm-api.idmap \
 	../ndbapi/metadata/overview.idmap \
 	../quick-guides/metadata/reservedwords-core.idmap \
+	../refman-4.1/metadata/installing.idmap \
 	../refman-4.1/metadata/sql-syntax-data-definition.idmap \
 	../refman-5.1-maria/metadata/se-maria-core.idmap \
 	../refman-5.1/metadata/mysql-cluster-backup.idmap \

@@ -930,6 +955,7 @@
 	../refman-common/images/published/PSEArch.png
 storage_engines_SOURCES = storage-engines.xml $(storage_engines_INCLUDES)
 storage_engines_IDMAPS = \
+	../refman-4.1/metadata/installing.idmap \
 	../refman-5.1-maria/metadata/se-maria-core.idmap \
 	../refman-5.1/metadata/backup.idmap \
 	../refman-5.1/metadata/dba-log-files.idmap \


Modified: trunk/refman-6.0/partitioning.xml
===================================================================
--- trunk/refman-6.0/partitioning.xml	2008-12-12 00:01:47 UTC (rev 12927)
+++ trunk/refman-6.0/partitioning.xml	2008-12-12 00:04:07 UTC (rev 12928)
Changed blocks: 1, Lines Added: 182, Lines Deleted: 33; 7798 bytes

@@ -3420,59 +3420,208 @@
         <secondary>repairing</secondary>
       </indexterm>
 
+      <indexterm>
+        <primary>ANALYZE TABLE</primary>
+        <secondary>and partitioning</secondary>
+      </indexterm>
+
+      <indexterm>
+        <primary>CHECK TABLE</primary>
+        <secondary>and partitioning</secondary>
+      </indexterm>
+
+      <indexterm>
+        <primary>OPTIMIZE TABLE</primary>
+        <secondary>and partitioning</secondary>
+      </indexterm>
+
+      <indexterm>
+        <primary>REPAIR TABLE</primary>
+        <secondary>and partitioning</secondary>
+      </indexterm>
+
       <para>
-        Beginning with MySQL 6.0.6, MySQL &current-series; supports the
-        statements <literal role="stmt">CHECK TABLE</literal>,
+        A number of table and partition maintenance tasks can be carried
+        out using SQL statements intended for such purposes on
+        partitioned tables in MySQL &current-series;.
+      </para>
+
+      <para>
+        Table maintenance of partitioned tables can be accomplished
+        using the statements <literal role="stmt">CHECK TABLE</literal>,
         <literal role="stmt">OPTIMIZE TABLE</literal>,
-        <literal role="stmt">ANALYZE TABLE</literal>, or
-        <literal role="stmt">REPAIR TABLE</literal> for partitioned
-        tables.
+        <literal role="stmt">ANALYZE TABLE</literal>, and
+        <literal role="stmt">REPAIR TABLE</literal>, which are supported
+        for partitioned tables as of MySQL 6.0.6.
       </para>
 
       <para>
-        You can also rebuild partitions in MySQL &current-series; using
-        <literal>ALTER TABLE ... REBUILD PARTITION</literal>, which has
-        the same effect as dropping all records stored in the partition,
-        then reinserting them. This can be useful for purposes of
-        defragmentation. You can rebuild a one or more partitions
-        belonging to the same table at one time using this statement, as
-        shown in these examples:
+        Also beginning with MySQL 6.0.6, you can use a number of
+        extensions to <literal role="stmt">ALTER TABLE</literal> for
+        performing operations of this type on one or more partitions
+        directly, as described in the following list:
+      </para>
 
+      <itemizedlist>
+
+        <listitem>
+          <formalpara>
+
+            <title>Rebuilding partitions</title>
+
+            <para>
+              Rebuilds the partition; this has the same effect as
+              dropping all records stored in the partition, then
+              reinserting them. This can be useful for purposes of
+              defragmentation.
+            </para>
+
+          </formalpara>
+
+          <para>
+            Example:
+          </para>
+
 <programlisting>
-ALTER TABLE t1 REBUILD PARTITION p1;
-ALTER TABLE t1 REBUILD PARTITION p0, p2;
+ALTER TABLE t1 REBUILD PARTITION p0, p1;
 </programlisting>
+        </listitem>
 
-        Executing the first statement rebuilds the partition named
-        <literal>p1</literal> from the table <literal>t1</literal>.
-        Performing the second statement rebuilds partitions
-        <literal>p0</literal> and <literal>p2</literal> from table
-        <literal>t1</literal>.
-      </para>
+        <listitem>
+          <formalpara>
 
-      <para>
-        <literal>ALTER TABLE ... REORGANIZE PARTITION</literal> also
-        causes partition files to be rebuilt.
-      </para>
+            <title>Optimizing partitions</title>
 
+            <para>
+              If you have deleted a large number of rows from a
+              partition or if you have made many changes to a
+              partitioned table with variable-length rows (that is,
+              having <literal>VARCHAR</literal>,
+              <literal>BLOB</literal>, or <literal>TEXT</literal>
+              columns), you can use <literal>ALTER TABLE ... OPTIMIZE
+              PARTITION</literal> to reclaim any unused space and to
+              defragment the partition data file.
+            </para>
+
+          </formalpara>
+
+          <para>
+            Example:
+          </para>
+
+<programlisting>
+ALTER TABLE t1 OPTIMIZE PARTITION p0, p1;
+</programlisting>
+
+          <para>
+            Using <literal>OPTIMIZE PARTITION</literal> on a given
+            partition is equivalent to running <literal>CHECK
+            PARTITION</literal>, <literal>ANALYZE PARTITION</literal>,
+            and <literal>REPAIR PARTITION</literal> on that partition.
+          </para>
+        </listitem>
+
+        <listitem>
+          <formalpara>
+
+            <title>Analyzing partitions</title>
+
+            <para>
+              This reads and stores the key distributions for
+              partitions.
+            </para>
+
+          </formalpara>
+
+          <para>
+            Example:
+          </para>
+
+<programlisting>
+ALTER TABLE t1 ANALYZE PARTITION p3;</programlisting>
+        </listitem>
+
+        <listitem>
+          <formalpara>
+
+            <title>Repairing partitions</title>
+
+            <para>
+              This repairs corrupted partitions.
+            </para>
+
+          </formalpara>
+
+          <para>
+            Example:
+          </para>
+
+<programlisting>
+ALTER TABLE t1 REPAIR PARTITION p0,p1;
+</programlisting>
+        </listitem>
+
+        <listitem>
+          <formalpara>
+
+            <title>Checking partitions</title>
+
+            <para>
+              You can check partitions for errors in much the same way
+              that you can use <literal>CHECK TABLE</literal> with
+              non-partitioned tables.
+            </para>
+
+          </formalpara>
+
+          <para>
+            Example:
+          </para>
+
+<programlisting>
+ALTER TABLE trb3 CHECK PARTITION p1;
+</programlisting>
+
+          <para>
+            This command will tell you if the data or indexes in
+            partition <literal>p1</literal> of table
+            <literal>t1</literal> are corrupted. If this is the case,
+            use <literal>ALTER TABLE ... REPAIR PARTITION</literal> to
+            repair the partition.
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
       <note>
         <para>
           The statements <literal>ALTER TABLE ... ANALYZE
           PARTITION</literal>, <literal>ALTER TABLE ... CHECK
           PARTITION</literal>, <literal>ALTER TABLE ... OPTIMIZE
           PARTITION</literal>, and <literal>ALTER TABLE ... REPAIR
-          PARTITION</literal> &mdash; intended to, respectively,
-          analyze, check, optimize, and repair individual or multiple
-          partitions &mdash; were removed in MySQL 6.0.5. (Bug #20129)
+          PARTITION</literal> did not work properly as originally
+          implemented, and were disabled in MySQL 6.0.5. They were
+          re-introduced in MySQL 6.0.6. (Bug #20129) The use of these
+          partitioning-specific <literal>ALTER TABLE</literal>
+          statements with tables which are not partitioned is not
+          supported; beginning with MySQL 6.0.8, it is expressly
+          disallowed. (Bug #39434)
         </para>
-
-        <para>
-          The use of <command>mysqlcheck</command> or
-          <command>myisamchk</command> is also not supported with
-          partitioned tables.
-        </para>
       </note>
 
+      <remark role="NOTE">
+        [js] Commented out following para, pending verification of the
+        statement contained therein.
+      </remark>
+
+<!--
+      <para>
+        The use of <command>mysqlcheck</command> and
+        <command>myisamchk</command> is also not supported with
+        partitioned tables.
+      </para>
+-->
+
     </section>
 
     <section id="partitioning-info">


Modified: trunk/refman-6.0/sql-syntax-data-definition.xml
===================================================================
--- trunk/refman-6.0/sql-syntax-data-definition.xml	2008-12-12 00:01:47 UTC (rev 12927)
+++ trunk/refman-6.0/sql-syntax-data-definition.xml	2008-12-12 00:04:07 UTC (rev 12928)
Changed blocks: 1, Lines Added: 20, Lines Deleted: 17; 3249 bytes

@@ -1751,34 +1751,37 @@
 
       <listitem>
         <para>
-          Several additional clauses were available in early MySQL 6.0
-          releases for providing partition maintenance and repair
-          functionality analogous to that implemented for
-          non-partitioned tables by statements such as
+          Several additional options available for providing partition
+          maintenance and repair functionality analogous to that
+          implemented for non-partitioned tables by statements such as
           <literal role="stmt">CHECK TABLE</literal> and
-          <literal role="stmt">REPAIR TABLE</literal> (which are
-          <emphasis>not</emphasis> supported for partitioned tables).
-          These include <literal>ANALYZE PARTITION</literal>,
-          <literal>CHECK PARTITION</literal>, <literal>OPTIMIZE
-          PARTITION</literal>, <literal>REBUILD PARTITION</literal>, and
-          <literal>REPAIR PARTITION</literal>. Each of these options
-          takes a <replaceable>partition_names</replaceable> clause
-          consisting of one or more names of partitions, separated by
-          commas. The partitions must already exist in the table to be
-          altered. For more information and examples, see
+          <literal role="stmt">REPAIR TABLE</literal> (which are are
+          also supported for partitioned tables, beginning with MySQL
+          6.0.6 &mdash; see note at the end of this item). These include
+          <literal>ANALYZE PARTITION</literal>, <literal>CHECK
+          PARTITION</literal>, <literal>OPTIMIZE PARTITION</literal>,
+          <literal>REBUILD PARTITION</literal>, and <literal>REPAIR
+          PARTITION</literal>. Each of these options takes a
+          <replaceable>partition_names</replaceable> clause consisting
+          of one or more names of partitions, separated by commas. The
+          partitions must already exist in the table to be altered. For
+          more information and examples, see
           <xref linkend="partitioning-maintenance"/>.
         </para>
 
         <para>
           The <literal>ANALYZE PARTITION</literal>, <literal>CHECK
           PARTITION</literal>, <literal>OPTIMIZE PARTITION</literal>,
-          and <literal>REPAIR PARTITION</literal> options were removed
-          in MySQL 6.0.5.
+          and <literal>REPAIR PARTITION</literal> options were disabled
+          in MySQL 6.0.5, and re-enabled in MySQL 6.0.6. (Bug #20129)
+          They are not supported for tables which are not partitioned;
+          beginning with MySQL 6.0.8, they are disallowed for such
+          tables.
         </para>
 
         <note>
           <para>
-            Beginning with MySQL 6.0.7, you can use the statements
+            Beginning with MySQL 6.0.6, you can use the statements
             <literal role="stmt">ANALYZE TABLE</literal>,
             <literal role="stmt">CHECK TABLE</literal>,
             <literal role="stmt">OPTIMIZE TABLE</literal>, and


Modified: trunk/refman-6.0/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-6.0/sql-syntax-server-administration.xml	2008-12-12 00:01:47 UTC (rev 12927)
+++ trunk/refman-6.0/sql-syntax-server-administration.xml	2008-12-12 00:04:07 UTC (rev 12928)
Changed blocks: 4, Lines Added: 22, Lines Deleted: 13; 3069 bytes

@@ -1827,8 +1827,12 @@
       </para>
 
       <para>
-        Beginning with MySQL 6.0.6, <literal role="stmt">ANALYZE
-        TABLE</literal> is also supported for partitioned tables.
+        Beginning with MySQL 6.0.8, <literal role="stmt">ANALYZE
+        TABLE</literal> is also supported for partitioned tables. Also
+        beginning with MySQL 6.0.8, you can use <literal>ALTER TABLE ...
+        ANALYZE PARTITION</literal> to analyze one or more partitions;
+        for more information, see <xref linkend="alter-table"/>, and
+        <xref linkend="partitioning-maintenance"/>.
       </para>
 
       <remark role="help-description-end"/>

@@ -1935,8 +1939,12 @@
       </para>
 
       <para>
-        <literal role="stmt">CHECK TABLE</literal> is not supported for
-        partitioned tables before MySQL 6.0.6.
+        Beginning with MySQL 6.0.6, <literal role="stmt">CHECK
+        TABLE</literal> is also supported for partitioned tables. Also
+        beginning with MySQL 6.0.6, you can use <literal>ALTER TABLE ...
+        CHECK PARTITION</literal> to check one or more partitions; for
+        more information, see <xref linkend="alter-table"/>, and
+        <xref linkend="partitioning-maintenance"/>.
       </para>
 
       <remark role="help-description-end"/>

@@ -2364,10 +2372,11 @@
 
       <para>
         Beginning with MySQL 6.0.6, <literal role="stmt">OPTIMIZE
-        TABLE</literal> is also supported for partitioned tables.
-        Additional statements can also be used for rebuilding partitions
-        &mdash; see <xref linkend="partitioning-maintenance"/>, for
-        information about these.
+        TABLE</literal> is also supported for partitioned tables. Also
+        beginning with MySQL 6.0.6, you can use <literal>ALTER TABLE ...
+        OPTIMIZE PARTITION</literal> to optimize one or more partitions;
+        for more information, see <xref linkend="alter-table"/>, and
+        <xref linkend="partitioning-maintenance"/>.
       </para>
 
       <remark role="help-description-end"/>

@@ -2535,11 +2544,11 @@
 
       <para>
         Beginning with MySQL 6.0.6, <literal role="stmt">REPAIR
-        TABLE</literal> is also supported for partitioned tables.
-        Additional statements exist which can be used for rebuilding
-        partitions &mdash; see
-        <xref linkend="partitioning-maintenance"/>, for information
-        about these.
+        TABLE</literal> is also supported for partitioned tables. Also
+        beginning with MySQL 6.0.6, you can use <literal>ALTER TABLE ...
+        REPAIR PARTITION</literal> to repair one or more partitions; for
+        more information, see <xref linkend="alter-table"/>, and
+        <xref linkend="partitioning-maintenance"/>.
       </para>
 
       <remark role="help-description-end"/>


Modified: trunk/topic-guides/topics-5.1/Makefile.depends
===================================================================
--- trunk/topic-guides/topics-5.1/Makefile.depends	2008-12-12 00:01:47 UTC (rev 12927)
+++ trunk/topic-guides/topics-5.1/Makefile.depends	2008-12-12 00:04:07 UTC (rev 12928)
Changed blocks: 4, Lines Added: 22, Lines Deleted: 3; 5292 bytes

@@ -414,7 +414,6 @@
 	../../refman-5.1/../refman-common/images/published/submaster-performance.png
 mysql_replication_excerpt_SOURCES = mysql-replication-excerpt.xml $(mysql_replication_excerpt_INCLUDES)
 mysql_replication_excerpt_IDMAPS = \
-		../../refman-5.1/metadata/backup.idmap \
 		../../refman-5.1/metadata/data-types.idmap \
 		../../refman-5.1/metadata/dba-log-files.idmap \
 		../../refman-5.1/metadata/dba-mysqld-server-core.idmap \

@@ -646,6 +645,16 @@
 	../../common/fixedchars.ent \
 	../../common/phrases.ent \
 	../../refman-5.1/errors-problems-core.xml \
+	../../refman-5.1/images/published/mysql-cfg-fig1.png \
+	../../refman-5.1/images/published/mysql-cfg-fig10.png \
+	../../refman-5.1/images/published/mysql-cfg-fig2.png \
+	../../refman-5.1/images/published/mysql-cfg-fig3.png \
+	../../refman-5.1/images/published/mysql-cfg-fig4.png \
+	../../refman-5.1/images/published/mysql-cfg-fig5.png \
+	../../refman-5.1/images/published/mysql-cfg-fig6.png \
+	../../refman-5.1/images/published/mysql-cfg-fig7.png \
+	../../refman-5.1/images/published/mysql-cfg-fig8.png \
+	../../refman-5.1/images/published/mysql-cfg-fig9.png \
 	../../refman-5.1/installing-core.xml \
 	../../refman-5.1/legalnotice.en.xml \
 	../../refman-5.1/versions.ent \

@@ -655,7 +664,17 @@
 	mysql-windows-excerpt-aspec.xml.resetting-permissions-windows.none.chapter.xml \
 	mysql-windows-excerpt-aspec.xml.windows-installation.none.chapter.xml \
 	mysql-windows-excerpt-aspec.xml.windows-source-build.none.chapter.xml
-mysql_windows_excerpt_IMAGES =
+mysql_windows_excerpt_IMAGES = \
+	../../refman-5.1/images/published/mysql-cfg-fig1.png \
+	../../refman-5.1/images/published/mysql-cfg-fig10.png \
+	../../refman-5.1/images/published/mysql-cfg-fig2.png \
+	../../refman-5.1/images/published/mysql-cfg-fig3.png \
+	../../refman-5.1/images/published/mysql-cfg-fig4.png \
+	../../refman-5.1/images/published/mysql-cfg-fig5.png \
+	../../refman-5.1/images/published/mysql-cfg-fig6.png \
+	../../refman-5.1/images/published/mysql-cfg-fig7.png \
+	../../refman-5.1/images/published/mysql-cfg-fig8.png \
+	../../refman-5.1/images/published/mysql-cfg-fig9.png
 mysql_windows_excerpt_SOURCES = mysql-windows-excerpt.xml $(mysql_windows_excerpt_INCLUDES)
 mysql_windows_excerpt_IDMAPS = \
 		../../refman-5.1/metadata/backup.idmap \

@@ -697,7 +716,7 @@
 	$(RM) mysql-startstop-excerpt.xml mysql-startstop-excerpt-arbitrary.xml
 	$(MAKE) mysql-startstop-excerpt.xml
 
-mysql-windows-excerpt-aspec.xml.can-not-connect-to-server-on-windows.none.chapter.xml mysql-windows-excerpt-aspec.xml.resetting-permissions-windows.none.chapter.xml mysql-windows-excerpt-aspec.xml.windows-installation.none.chapter.xml mysql-windows-excerpt-aspec.xml.windows-source-build.none.chapter.xml: ../../common/fixedchars.ent ../../common/phrases.ent ../../refman-5.1/errors-problems-core.xml ../../refman-5.1/versions.ent ../../refman-common/urls.ent all-entities.ent ../../common/fixedchars.ent ../../common/phrases.ent ../../refman-5.1/errors-problems-core.xml ../../refman-5.1/versions.ent ../../refman-common/urls.ent all-entities.ent ../../common/fixedchars.ent ../../common/phrases.ent ../../refman-5.1/installing-core.xml ../../refman-5.1/versions.ent ../../refman-common/urls.ent all-entities.ent ../../common/fixedchars.ent ../../common/phrases.ent ../../refman-5.1/installing-core.xml ../../refman-5.1/versions.ent ../../refman-common/urls.ent all-entities.ent
+mysql-windows-excerpt-aspec.xml.can-not-connect-to-server-on-windows.none.chapter.xml mysql-windows-excerpt-aspec.xml.resetting-permissions-windows.none.chapter.xml mysql-windows-excerpt-aspec.xml.windows-installation.none.chapter.xml mysql-windows-excerpt-aspec.xml.windows-source-build.none.chapter.xml: ../../common/fixedchars.ent ../../common/phrases.ent ../../refman-5.1/errors-problems-core.xml ../../refman-5.1/versions.ent ../../refman-common/urls.ent all-entities.ent ../../common/fixedchars.ent ../../common/phrases.ent ../../refman-5.1/errors-problems-core.xml ../../refman-5.1/versions.ent ../../refman-common/urls.ent all-entities.ent ../../common/fixedchars.ent ../../common/phrases.ent ../../refman-5.1/images/published/mysql-cfg-fig1.png ../../refman-5.1/images/published/mysql-cfg-fig10.png ../../refman-5.1/images/published/mysql-cfg-fig2.png ../../refman-5.1/images/published/mysql-cfg-fig3.png ../../refman-5.1/images/published/mysql-cfg-fig4.png ../../refman-5.1/imag!
 es/published/mysql-cfg-fig5.png ../../refman-5.1/images/published/mysql-cfg-fig6.png ../../refman-5.1/images/published/mysql-cfg-fig7.png ../../refman-5.1/images/published/mysql-cfg-fig8.png ../../refman-5.1/images/published/mysql-cfg-fig9.png ../../refman-5.1/installing-core.xml ../../refman-5.1/versions.ent ../../refman-common/urls.ent all-entities.ent ../../common/fixedchars.ent ../../common/phrases.ent ../../refman-5.1/installing-core.xml ../../refman-5.1/versions.ent ../../refman-common/urls.ent all-entities.ent
 	$(RM) mysql-windows-excerpt.xml mysql-windows-excerpt-arbitrary.xml
 	$(MAKE) mysql-windows-excerpt.xml
 


Modified: trunk/topic-guides/topics-6.0/Makefile.depends
===================================================================
--- trunk/topic-guides/topics-6.0/Makefile.depends	2008-12-12 00:01:47 UTC (rev 12927)
+++ trunk/topic-guides/topics-6.0/Makefile.depends	2008-12-12 00:04:07 UTC (rev 12928)
Changed blocks: 4, Lines Added: 22, Lines Deleted: 3; 5292 bytes

@@ -333,7 +333,6 @@
 	../../refman-6.0/../refman-common/images/published/submaster-performance.png
 mysql_replication_excerpt_SOURCES = mysql-replication-excerpt.xml $(mysql_replication_excerpt_INCLUDES)
 mysql_replication_excerpt_IDMAPS = \
-		../../refman-6.0/metadata/backup.idmap \
 		../../refman-6.0/metadata/data-types.idmap \
 		../../refman-6.0/metadata/dba-log-files.idmap \
 		../../refman-6.0/metadata/dba-mysqld-server-core.idmap \

@@ -565,6 +564,16 @@
 	../../common/fixedchars.ent \
 	../../common/phrases.ent \
 	../../refman-5.1/errors-problems-core.xml \
+	../../refman-5.1/images/published/mysql-cfg-fig1.png \
+	../../refman-5.1/images/published/mysql-cfg-fig10.png \
+	../../refman-5.1/images/published/mysql-cfg-fig2.png \
+	../../refman-5.1/images/published/mysql-cfg-fig3.png \
+	../../refman-5.1/images/published/mysql-cfg-fig4.png \
+	../../refman-5.1/images/published/mysql-cfg-fig5.png \
+	../../refman-5.1/images/published/mysql-cfg-fig6.png \
+	../../refman-5.1/images/published/mysql-cfg-fig7.png \
+	../../refman-5.1/images/published/mysql-cfg-fig8.png \
+	../../refman-5.1/images/published/mysql-cfg-fig9.png \
 	../../refman-5.1/installing-core.xml \
 	../../refman-5.1/legalnotice.en.xml \
 	../../refman-6.0/versions.ent \

@@ -574,7 +583,17 @@
 	mysql-windows-excerpt-aspec.xml.resetting-permissions-windows.none.chapter.xml \
 	mysql-windows-excerpt-aspec.xml.windows-installation.none.chapter.xml \
 	mysql-windows-excerpt-aspec.xml.windows-source-build.none.chapter.xml
-mysql_windows_excerpt_IMAGES =
+mysql_windows_excerpt_IMAGES = \
+	../../refman-5.1/images/published/mysql-cfg-fig1.png \
+	../../refman-5.1/images/published/mysql-cfg-fig10.png \
+	../../refman-5.1/images/published/mysql-cfg-fig2.png \
+	../../refman-5.1/images/published/mysql-cfg-fig3.png \
+	../../refman-5.1/images/published/mysql-cfg-fig4.png \
+	../../refman-5.1/images/published/mysql-cfg-fig5.png \
+	../../refman-5.1/images/published/mysql-cfg-fig6.png \
+	../../refman-5.1/images/published/mysql-cfg-fig7.png \
+	../../refman-5.1/images/published/mysql-cfg-fig8.png \
+	../../refman-5.1/images/published/mysql-cfg-fig9.png
 mysql_windows_excerpt_SOURCES = mysql-windows-excerpt.xml $(mysql_windows_excerpt_INCLUDES)
 mysql_windows_excerpt_IDMAPS = \
 		../../refman-6.0/metadata/backup.idmap \

@@ -616,7 +635,7 @@
 	$(RM) mysql-startstop-excerpt.xml mysql-startstop-excerpt-arbitrary.xml
 	$(MAKE) mysql-startstop-excerpt.xml
 
-mysql-windows-excerpt-aspec.xml.can-not-connect-to-server-on-windows.none.chapter.xml mysql-windows-excerpt-aspec.xml.resetting-permissions-windows.none.chapter.xml mysql-windows-excerpt-aspec.xml.windows-installation.none.chapter.xml mysql-windows-excerpt-aspec.xml.windows-source-build.none.chapter.xml: ../../common/fixedchars.ent ../../common/phrases.ent ../../refman-5.1/errors-problems-core.xml ../../refman-6.0/versions.ent ../../refman-common/urls.ent all-entities.ent ../../common/fixedchars.ent ../../common/phrases.ent ../../refman-5.1/errors-problems-core.xml ../../refman-6.0/versions.ent ../../refman-common/urls.ent all-entities.ent ../../common/fixedchars.ent ../../common/phrases.ent ../../refman-5.1/installing-core.xml ../../refman-6.0/versions.ent ../../refman-common/urls.ent all-entities.ent ../../common/fixedchars.ent ../../common/phrases.ent ../../refman-5.1/installing-core.xml ../../refman-6.0/versions.ent ../../refman-common/urls.ent all-entities.ent
+mysql-windows-excerpt-aspec.xml.can-not-connect-to-server-on-windows.none.chapter.xml mysql-windows-excerpt-aspec.xml.resetting-permissions-windows.none.chapter.xml mysql-windows-excerpt-aspec.xml.windows-installation.none.chapter.xml mysql-windows-excerpt-aspec.xml.windows-source-build.none.chapter.xml: ../../common/fixedchars.ent ../../common/phrases.ent ../../refman-5.1/errors-problems-core.xml ../../refman-6.0/versions.ent ../../refman-common/urls.ent all-entities.ent ../../common/fixedchars.ent ../../common/phrases.ent ../../refman-5.1/errors-problems-core.xml ../../refman-6.0/versions.ent ../../refman-common/urls.ent all-entities.ent ../../common/fixedchars.ent ../../common/phrases.ent ../../refman-5.1/images/published/mysql-cfg-fig1.png ../../refman-5.1/images/published/mysql-cfg-fig10.png ../../refman-5.1/images/published/mysql-cfg-fig2.png ../../refman-5.1/images/published/mysql-cfg-fig3.png ../../refman-5.1/images/published/mysql-cfg-fig4.png ../../refman-5.1/imag!
 es/published/mysql-cfg-fig5.png ../../refman-5.1/images/published/mysql-cfg-fig6.png ../../refman-5.1/images/published/mysql-cfg-fig7.png ../../refman-5.1/images/published/mysql-cfg-fig8.png ../../refman-5.1/images/published/mysql-cfg-fig9.png ../../refman-5.1/installing-core.xml ../../refman-6.0/versions.ent ../../refman-common/urls.ent all-entities.ent ../../common/fixedchars.ent ../../common/phrases.ent ../../refman-5.1/installing-core.xml ../../refman-6.0/versions.ent ../../refman-common/urls.ent all-entities.ent
 	$(RM) mysql-windows-excerpt.xml mysql-windows-excerpt-arbitrary.xml
 	$(MAKE) mysql-windows-excerpt.xml
 


Thread
svn commit - mysqldoc@docsrva: r12928 - in trunk: dynamic-docs/changelog mysql-monitor-2.0 refman-5.1 refman-5.1-maria refman-6.0 topic-guides/topics-...jon12 Dec