db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Fischer (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-142) ResultSetMetaData.isReadOnly() also returns wrong results
Date Sat, 12 Feb 2005 11:48:13 GMT
     [ http://issues.apache.org/jira/browse/DERBY-142?page=history ]

Thomas Fischer updated DERBY-142:
---------------------------------

    Attachment: DerbyTest.java

Testcase for ResultSetMetaData.isReadOnly(). 
The db2 universal Driver libraries should be in the classpath; a Derby network server should
be running on localhost and a database named test should exist on that server in order to
be able to run the test case

> 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
>
> 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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message