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] Closed: (DERBY-143) ResultSetMetaData.isReadOnly() also returns wrong results
Date Mon, 23 Jan 2006 20:29:10 GMT
     [ http://issues.apache.org/jira/browse/DERBY-143?page=all ]
     
Satheesh Bandaram closed DERBY-143:
-----------------------------------

    Resolution: Duplicate

Duplicate of DERBY-142. Seems like multiple entries were created for this... DERBY-142, DERBY-143
and DERBY-144. Closing the last two.

> ResultSetMetaData.isReadOnly() also returns wrong results
> ---------------------------------------------------------
>
>          Key: DERBY-143
>          URL: http://issues.apache.org/jira/browse/DERBY-143
>      Project: Derby
>         Type: Sub-task
>   Components: JDBC
>     Versions: 10.0.2.1
>  Environment: Using DB2 universal driver with standalone derby server
>     Reporter: Thomas Fischer

>
> 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