db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-142) ResultSetMetaData.isReadOnly() also returns wrong results
Date Mon, 17 Aug 2009 10:56:15 GMT

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

Knut Anders Hatlen updated DERBY-142:
-------------------------------------

      Issue & fix info: [Repro attached]
               Urgency: Normal
    Bug behavior facts: [Deviation from standard, Embedded/Client difference]

> 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