If this issue has not explicitly stated on the Torque website then I think it would be a good idea to do that.
Cause it took me hours to debug and find out what the problem was. Or somehow get a better stack trace or log message. Thanks Vikas -----Original Message----- From: Andras Balogh [mailto:[EMAIL PROTECTED] Sent: Thursday, January 22, 2004 12:54 AM To: Apache Torque Users List Subject: Re: DB2/400 inserts fail with Torque code Hello, We had the same problem using Sybase DB, and we did exactly the same, modified the village classes to set readonly=false. I think only ResultSetMetaData can return the meta data of a table (i.e. column info) and not DatabaseMetaData. Best wishes, Andras. Vikas Phonsa wrote: >Hi, > > > > > > > >I can't insert data into my DB2/400 using the torque generated classes. The >reason is the ResultSetMetaData obtained from the ResultSet returned by the >Select statement before the Inserts in Torque code, gives all my columns to >be readOnly. This is not pointed out in the exception stacks that I get but >I did manually debugging to find that out. > > > >Manually setting readonly=false in the workingdogs code fixes the problem. > > > >Has anybody in here faced similar issues with DB2/400 or any other database? > > > >And why is ResultSetMetaData being used instead of DatabaseMetaData ? > > > >And is there anybody in this list who is currently using Torque successfully >with DB2/400 ? > > > > > >Thanks > > > > > >Vikas Phonsa > > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
