Hi, We have made tests on db2 on iSeries V4r5 with torque 3.0 beta 2.
The main problem we have found is the support of meta-data on a JDBC connection. By defaut, the read only attribute for a column is not retrieve by the JDBC driver and is always set to false; in this case, the village API 1.5.3 will not be able to insert or update record on an iSeries db2 database. The workaround is to bypass method com.workingdogs.village.Column.readOnly() which should always return true (not elegant but work for our tests). We have also found problems on the DB adapter : on iSeries two JDBC drivers exist : one named com.ibm.as400.access.AS400JDBCDriver (this is a type 4 driver which can be executed on every machine) and an other one named com.ibm.db2.jdbc.app.DB2Driver (this is a type 2 driver which can be executed only on the iSeries platform). The second driver cannot be used without modification of the org.apache.torque.adapter.DBFactory : we had to modify the "JDBC driver to Torque adapter map" to suppress the conflict with the COM.ibm.db2.jdbc.app.DB2Driver driver used in DB2 Universal. Regards, Arnaud Dessert. -----Message d'origine----- De: Joy Alamgir [SMTP:[EMAIL PROTECTED]] Date: mardi 2 juillet 2002 19:34 A: [EMAIL PROTECTED] Objet: lazy loading and on a separate issue: db2 Hello, I was wondering if anyone gave any thought on lazy loading related objects in torque. If not, I would like to contribute in developing that. And on a different issue, is anyone working on testing torque of db2? Regards, Joy Alamgir [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
