Author: tfischer
Date: Fri Sep 10 03:49:40 2010
New Revision: 995660
URL: http://svn.apache.org/viewvc?rev=995660&view=rev
Log:
TORQUE-130: remove the heavyIndexing attribute from database and table elements
Modified:
db/torque/torque4/trunk/torque-site/src/changes/changes.xml
db/torque/torque4/trunk/torque-templates/src/main/resources/org/apache/torque/templates/xsd/database-4-0.xsd
Modified: db/torque/torque4/trunk/torque-site/src/changes/changes.xml
URL:
http://svn.apache.org/viewvc/db/torque/torque4/trunk/torque-site/src/changes/changes.xml?rev=995660&r1=995659&r2=995660&view=diff
==============================================================================
--- db/torque/torque4/trunk/torque-site/src/changes/changes.xml (original)
+++ db/torque/torque4/trunk/torque-site/src/changes/changes.xml Fri Sep 10
03:49:40 2010
@@ -24,6 +24,13 @@
<body>
<release version="4.0-alpha1-SNAPSHOT" date="in SVN">
+ <action type="remove" dev="gmonroe" issue="TORQUE-130">
+ Remove the heavyIndexing attribute for the elements table and database
+ in schema XML files.
+ This has not worked correctly in the past.
+ Users who have set this attribute in old schema XMLs,
+ please define their indices using index elements.
+ </action>
<action type="remove" dev="gmonroe" issue="TORQUE-91">
Remove the size attribute for the element index-column
in schema XML files.
Modified:
db/torque/torque4/trunk/torque-templates/src/main/resources/org/apache/torque/templates/xsd/database-4-0.xsd
URL:
http://svn.apache.org/viewvc/db/torque/torque4/trunk/torque-templates/src/main/resources/org/apache/torque/templates/xsd/database-4-0.xsd?rev=995660&r1=995659&r2=995660&view=diff
==============================================================================
---
db/torque/torque4/trunk/torque-templates/src/main/resources/org/apache/torque/templates/xsd/database-4-0.xsd
(original)
+++
db/torque/torque4/trunk/torque-templates/src/main/resources/org/apache/torque/templates/xsd/database-4-0.xsd
Fri Sep 10 03:49:40 2010
@@ -152,21 +152,6 @@ objects. There are three different optio
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="heavyIndexing" use="optional" type="xs:boolean"
- default="false" >
- <xs:annotation>
- <xs:documentation xml:lang="en">
-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 PRIMARY KEY (FOO_ID, BAR_ID), FOO_ID must be the
first
-element used in the where 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.
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
<xs:attribute name="defaultJavaType" use="optional"
type="javaReturnType" default="primitive" >
<xs:annotation>
@@ -332,14 +317,6 @@ The table name of the SQL table.
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="heavyIndexing" use="optional"
- type="xs:boolean" >
- <xs:annotation>
- <xs:documentation xml:lang="en">
-See heavyIndexing attribute in the database element.
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
<xs:attribute name="interface" type="javaQualifiedNameType"
use="optional" >
<xs:annotation>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
