db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Satheesh Bandaram (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-142) ResultSetMetaData.isReadOnly() also returns wrong results
Date Wed, 12 Oct 2005 18:59:06 GMT
    [ http://issues.apache.org/jira/browse/DERBY-142?page=comments#action_12331916 ] 

Satheesh Bandaram commented on DERBY-142:
-----------------------------------------

Thanks, Thomas for your detailed comment. I tested on DB2, that I have access to. Using their
Universal JCC driver against 8.15 server, it seems DB2 interprets "designated column" to mean
the result column, not the base table column. Without FOR UPDATE, DB2 server returns isReadOnly()
to TRUE. With FOR UPDATE clause, it returns FALSE.

I haven't tried against other database vendors. Just wanted to add this info. I am willing
to address the issue eitherway once we reach a consesus here.

> 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


Mime
View raw message