[
https://issues.apache.org/jira/browse/DERBY-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12917559#action_12917559
]
Knut Anders Hatlen commented on DERBY-545:
------------------------------------------
That text was removed in JDBC 4.0. Now it says the following in 15.2.5
Closing a ResultSet Object:
,----
| A ResultSet object is implicitly closed when
| ■ The associated Statement object is re-executed
| ■ The ResultSet is created with a Holdability of
| CLOSE_CURSORS_AT_COMMIT and an implicit or explicit commit occurs
|
| Note - Some JDBC driver implementations may also implicitly close the
| ResultSet when the ResultSet type is TYPE_FORWARD_ONLY and the next
| method of ResultSet returns false.
`----
So I think the behaviour implemented in DERBY-213 complies with the
JDBC 4.0 specification. Unless there are objections, I'll close this
issue 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: 10.0.2.0, 10.0.2.1, 10.0.2.2, 10.1.1.0, 10.1.2.1,
> 10.2.1.6
> 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/%[email protected]%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/%[email protected]%3e
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
