Author: pcl
Date: Tue Jan 2 19:09:52 2007
New Revision: 492035
URL: http://svn.apache.org/viewvc?view=rev&rev=492035
Log:
some docs about MySQL optimization
Modified:
incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml
Modified:
incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml
URL:
http://svn.apache.org/viewvc/incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml?view=diff&rev=492035&r1=492034&r2=492035
==============================================================================
---
incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml
(original)
+++
incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml
Tue Jan 2 19:09:52 2007
@@ -2447,6 +2447,27 @@
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">
