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]



Reply via email to