You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Anonymous (JIRA)" <de...@db.apache.org> on 2005/10/07 20:10:48 UTC
[jira] Updated: (DERBY-142) ResultSetMetaData.isReadOnly() also returns wrong results
[ http://issues.apache.org/jira/browse/DERBY-142?page=all ]
updated DERBY-142:
-------------------
Attachment: DerbyTest142.java
> 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