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] Commented: (DERBY-1744) ResultSet.rowInserted(), rowUpdated() and rowDeleted() don't throw exception on read-only result sets
Date Fri, 25 Aug 2006 09:00:23 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1744?page=comments#action_12430452 ] 
            
Knut Anders Hatlen commented on DERBY-1744:
-------------------------------------------

Thanks for your comments, Dag. There already are similar changes in these methods from 10.1
to 10.2. For instance, DERBY-1323 changed the behaviour of these methods, and it has both
the Existing Application Impact and the Release Note Needed flags. Standards compliace is
a good thing, so I would say we should change it and have a release note that mentions these
changes and the changes in DERBY-1323 together.

One problem I have come across, is that the network server calls these methods on read-only
result sets. Because of the way Derby implements updatable result sets and positioned updates,
it is possible that the methods return true on a read-only result set with an updatable cursor.
Since the spec says they should raise an error when the result set is true, these methods
cannot be used to check if a row in read-only result set has been changed with a positioned
update. I haven't found a way to work around this yet.

> 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