db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-545) Should ResultSet Close implicitly?
Date Wed, 13 Oct 2010 12:46:33 GMT

     [ https://issues.apache.org/jira/browse/DERBY-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Knut Anders Hatlen closed DERBY-545.

    Resolution: Not A Problem

No objections were raised. Closing as Not A Problem.

> Should ResultSet Close implicitly?
> ----------------------------------
>                 Key: DERBY-545
>                 URL: https://issues.apache.org/jira/browse/DERBY-545
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>    Affects Versions:,,,,,
>            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
for FORWARD_ONLY ResultSets.
> 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:
> http://mail-archives.apache.org/mod_mbox/db-derby-dev/200506.mbox/%3c42BC0C49.3030403@acadiau.ca%3e
> Here is my summary of my meeting with the JDBC 4.0 EG in an attempt to resolve this issue:
> http://mail-archives.apache.org/mod_mbox/db-derby-dev/200507.mbox/%3c42E80ED0.7080505@acadiau.ca%3e

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message