[ http://issues.apache.org/jira/browse/DERBY-142?page=comments#action_12331917 ]
Daniel John Debrunner commented on DERBY-142: --------------------------------------------- Satheesh, just to be clear in your last test what was the updateability of the JDBC ResultSet? Can you repeat the test with a non-updateable result set? I thought with DB2 (and the SQL standard) that a SELECT statement was always updatable with a positioned update, thus FOR UPDATE would not make a difference. Might be interesting to try the SELECT statement with FOR READ ONLY. > 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: 10.0.2.1 > Environment: Using DB2 universal driver with standalone derby server > Reporter: Thomas Fischer > Attachments: DerbyTest.java, DerbyTest142.java > > ResultSetMetaData.isReadOnly() always returns true, even when writing to the > table is possible. > 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: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
