You can view the issue detail at the following URL:
<http://nagoya.apache.org/scarab/issues/id/TRQS39>
Type : Defect
Issue Id : TRQS39
Reported by: Rodney Schneider
rodney - ([EMAIL PROTECTED])
Details:
Summary: id-table-init-sql generates unwanted ID_TABLE inserts
Description: At the moment, the "id-table-init-sql" target in build-torque.xml
generates inserts into the ID_TABLE for all tables in the various *-schema.xml files
of a Torque project. These end up in the *-schema-idtable-init.sql files, which are
the output files of the "torque-sql" task that is executed as part of the target.
However, the "id-table-init-sql" target should not generate inserts into the ID_TABLE
for tables that have idMethod="native" or idMethod="none" in a *-schema.xml file.
This bug causes extra unwanted entries to be inserted into the ID_TABLE.
I found the following property in the default.properties file of my Torque jar file:
torque.schema.init-sql.excludes = id-table-schema.xml
I am currently migrating my TDK-2.1 application to TDK-2.2b3. As a
work-around, so that I could get "ant init" to run without errors, I added the
following line to my build.properties file:
torque.schema.init-sql.excludes = id-table-schema.xml,kahootz-schema.xml
BTW, kahootz-schema.xml is my webapp's Torque schema file and all of the tables in it
have idMethod="native", so the kahootz-schema-idtable-init.sql file that is generated
by the "id-table-init-sql" should not contain any inserts at all (actually, it doesn't
even need to be generated). I use MySQL 3.23.42 on Redhat 7.2.
IMHO, if there are no tables that have idMethod="idbroker" in a Torque *-schema file,
the *-schema-idtable-init.sql should not even be created by the "id-table-init-sql"
target.
Status: New
Database: MySQL
Operating system: Linux
Priority: High
--
To unsubscribe, e-mail: <mailto:turbine-torque-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:turbine-torque-dev-help@;jakarta.apache.org>
