Re: Will migrating from 3.0 to 3.3 help me?
"Richard Walker" <[email protected]>
| Newsgroups | gmane.comp.jakarta.turbine.torque.user |
|---|---|
| Message-ID | <[email protected]> |
>> How about you make yourself a copy of village.jar with the offending lines
>> in the Column class commented out and see if your queries still execute
>> correctly. Really this would just be the opposite of having the stub
>> methods in the old JDBC driver. Provided your application is not accessing
>> the metadata present in the Column class (directly or indirectly) this
>> should be a valid approach.
I've traced the extra queries to these two lines in Column.java:
this.nullAllowed = rsmd.isNullable(columnNumber) == 1;
this.autoIncrement = rsmd.isAutoIncrement(columnNumber);
I checked the source of the old driver; it hard-codes the
results of those queries, so this.nullAllowed and this.autoIncrement
are always set to false.
So I made this modification:
this.nullAllowed = false; // rsmd.isNullable(columnNumber) == 1;
this.autoIncrement = false; // rsmd.isAutoIncrement(columnNumber);
And it works! No more extra queries.
Problem solved - for me, anyway.
Thanks for the hints.