db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-142) ResultSetMetaData.isReadOnly() also returns wrong results
Date Thu, 08 Mar 2007 18:13:24 GMT

    [ https://issues.apache.org/jira/browse/DERBY-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479374
] 

Kathey Marsden commented on DERBY-142:
--------------------------------------

In a discussion on derby-dev, Lance (JDBC expert) said

"i would recommend returning false as this returned result is not tied to an updatable ResultSet
but to whether you can definitively determine the column cannot be modified.  This is a JDBC
1.0 method."


So if noone objects the correst resolution of this issue is to change client to match embedded.





> ResultSetMetaData.isReadOnly() also returns wrong results
> ---------------------------------------------------------
>
>                 Key: DERBY-142
>                 URL: https://issues.apache.org/jira/browse/DERBY-142
>             Project: Derby
>          Issue Type: Sub-task
>          Components: JDBC
>    Affects Versions: 10.0.2.1
>         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
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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message