db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Fischer (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-142) ResultSetMetaData.isReadOnly() also returns wrong results
Date Mon, 17 Oct 2005 19:52:45 GMT
    [ http://issues.apache.org/jira/browse/DERBY-142?page=comments#action_12332283 ] 

Thomas Fischer commented on DERBY-142:

Hm, let's not get too Torque-centric here. If the derby developers decide that the current
behaviour of the network driver is correct, that is ok with me, I can see the reasons for
it now. I was probably a bit naive when I reported this as a 'bug'.

Another thing, if you think it would be helpful to know how other databases interpret the
isReadOnly function, I can offer to run Satheesh's test program against some other databases
(mysql, postgresql, oracle, firebird, hsqldb). Just let me know.

> ResultSetMetaData.isReadOnly() also returns wrong results
> ---------------------------------------------------------
>          Key: DERBY-142
>          URL: http://issues.apache.org/jira/browse/DERBY-142
>      Project: Derby
>         Type: Sub-task
>   Components: JDBC
>     Versions:
>  Environment: Using DB2 universal driver with standalone derby server
>     Reporter: Thomas Fischer
>  Attachments: DerbyTest.java, DerbyTest142.java, TorqueTutorial.txt
> ResultSetMetaData.isReadOnly() always returns true, even when writing to the table is
> The JDBC 2.0 spec says: "ResultSetMetaData.isReadOnly() : Indicates whether the designated
column is definitely not writable.", so the method should return false for a table.
> I will attach a testcase for this behaviour.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message