From f69eb137143b7b67f947e4be25ddc1d8a02ff496 Mon Sep 17 00:00:00 2001
From: Patrick Linskey <pcl@apache.org>
Date: Wed, 3 Jan 2007 03:09:52 +0000
Subject: [PATCH] some docs about MySQL optimization

git-svn-id: https://svn.apache.org/repos/asf/incubator/openjpa/trunk@492035 13f79535-47bb-0310-9956-ffa450edef68
---
 .../src/doc/manual/ref_guide_dbsetup.xml      | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml b/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml
index babd1de60..82bc997c9 100644
--- a/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml
+++ b/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml
@@ -2447,6 +2447,27 @@ correctly. To enable clob functionality, set this to true. Defaults to <literal>
 false</literal>.
                     </para>
                 </listitem>
+                <listitem id="MySQLDictionary.OptimizeMultiTableDeletes">
+                    <para>
+                    <indexterm>
+                        <primary>
+                            MySQL
+                        </primary>
+                        <secondary>
+                            OptimizeMultiTableDeletes
+                        </secondary>
+                    </indexterm>
+<literal>OptimizeMultiTableDeletes</literal>: MySQL as of version 4.0.0
+supports multiple tables in <literal>DELETE</literal> statements. When
+this option is set, OpenJPA will use that syntax when doing bulk deletes
+from multiple tables. This can happen when the
+<literal>deleteTableContents</literal> <literal>SchemaTool</literal>
+action is used. (See <xref linkend="ref_guide_schema_schematool"/> for
+more info about <literal>deleteTableContents</literal>.) Defaults to
+<literal>false</literal>, since the statement may fail if using InnoDB
+tables and delete constraints.
+                    </para>
+                </listitem>
             </itemizedlist>
         </section>
         <section id="ref_guide_dbsetup_dbsupport_oracle">