[ http://issues.apache.org/jira/browse/DERBY-545?page=all ]
Philip Wilder updated DERBY-545:
--------------------------------
Description:
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]
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]
was:
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:
http://mail-archives.apache.org/mod_mbox/db-derby-dev/200506.mbox/[EMAIL
PROTECTED]
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]
Thanks for the forward only clarification Bernt
> Should ResultSet Close implicitly?
> ----------------------------------
>
> Key: DERBY-545
> URL: http://issues.apache.org/jira/browse/DERBY-545
> Project: Derby
> Type: Improvement
> Components: JDBC
> Versions: 10.0.2.0, 10.0.2.1, 10.0.2.2, 10.1.1.0, 10.2.0.0, 10.1.1.1
> 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]
> 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]
--
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
