[ http://issues.apache.org/jira/browse/DERBY-1744?page=comments#action_12430327 ] Dag H. Wanvik commented on DERBY-1744: --------------------------------------
We noticed this in the SUR work, but chose not to change it for fear of affecting exisiting apps. Do we want to change it? > 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
