You are viewing a plain text version of this content. The canonical link for it is here.
Posted to torque-dev@db.apache.org by dl...@apache.org on 2003/06/27 00:10:49 UTC
cvs commit: db-torque/src/generator/xdocs schema-reference.xml
dlr 2003/06/26 15:10:49
Modified: src/generator/xdocs schema-reference.xml
Log:
* src/generator/xdocs/schema-reference.xml
heavyIndexing: Added documenation pulled from the JavaDoc of
org.apache.torque.engine.database.model.Table's doHeavyIndexing()
method.
Revision Changes Path
1.2 +13 -1 db-torque/src/generator/xdocs/schema-reference.xml
Index: schema-reference.xml
===================================================================
RCS file: /home/cvs/db-torque/src/generator/xdocs/schema-reference.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -u -r1.1 -r1.2
--- schema-reference.xml 26 Jun 2003 21:41:36 -0000 1.1
+++ schema-reference.xml 26 Jun 2003 22:10:49 -0000 1.2
@@ -78,7 +78,19 @@
</tr>
<tr>
<td>heavyIndexing</td>
- <td>? (true or false, defaults to false)</td>
+ <td>Adds extra indices for multi-part primary key
+ columns. true or false, defaults to false.
+
+ For databases like MySQL, values in a where clause
+ must match key part order from the left to right.
+ So, in the key definition <code>PRIMARY KEY (FOO_ID,
+ BAR_ID)</code>, <code>FOO_ID</code> <i>must</i> be
+ the first element used in the <code>where</code>
+ clause of the SQL query used against this table for
+ the primary key index to be used. This feature could
+ cause problems under MySQL with heavily indexed
+ tables, by causing too many indices to be created
+ (overrunning MySQL's table limit).</p></td>
</tr>
</table>
</p>