db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Wilder (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-545) Should ResultSet Close implicitly?
Date Tue, 30 Aug 2005 12:22:07 GMT
Should ResultSet Close implicitly?

         Key: DERBY-545
         URL: http://issues.apache.org/jira/browse/DERBY-545
     Project: Derby
        Type: Improvement
  Components: JDBC  
 Reporter: Philip Wilder
    Priority: Minor

While work on DERBY-213 has resulted in a client ResultSet that matches the functionality
of embedded ResultSet it is possible that both embedded and client are now wrong.

According to the JDBC 3.0 specification:

"For Select statements, the statement is complete when the associated result set is 
closed. The result set is closed as soon as one of the following occurs: 
- all of the rows have been retrieved"

At the moment ResultSets will only close implicitly if holdability is set to CLOSE_CURSORS_AT_COMMIT.

The following is a link to some related work, done while working on DERBY-213. This is potential
document outlining Derby's policy on auto-commit behavior:

Here is my summary of my meeting with the JDBC 4.0 EG in an attempt to resolve this issue:

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message