db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Closed: (DERBY-1744) ResultSet.rowInserted(), rowUpdated() and rowDeleted() don't throw exception on read-only result sets
Date Mon, 28 Aug 2006 17:27:23 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1744?page=all ]

Knut Anders Hatlen closed DERBY-1744.
-------------------------------------

    Resolution: Invalid

Thanks to Dag and Lance for clearing this up. Closing the issue as invalid.

> ResultSet.rowInserted(), rowUpdated() and rowDeleted() don't throw exception on read-only
result sets
> -----------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1744
>                 URL: http://issues.apache.org/jira/browse/DERBY-1744
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.0.2.1
>            Reporter: Knut Anders Hatlen
>         Assigned To: Knut Anders Hatlen
>            Priority: Minor
>
> These methods should throw SQLException if concurrency is CONCUR_READ_ONLY. See http://download.java.net/jdk6/docs/api/java/sql/ResultSet.html:
> Throws:
>     SQLException - if a database access error occurs; the result set concurrency is CONCUR_READ_ONLY
or this method is called on a closed result set

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