You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Philip Wilder (JIRA)" <de...@db.apache.org> on 2005/08/30 14:22:07 UTC

[jira] Created: (DERBY-545) Should ResultSet Close implicitly?

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.

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.
-
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


Re: [jira] Created: (DERBY-545) Should ResultSet Close implicitly?

Posted by "Bernt M. Johnsen" <Be...@Sun.COM>.
>>>>>>>>>>>> Philip Wilder (JIRA) wrote (2005-08-30 14:22:07):
> 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.

Implict close should also apply only to TYPE_FORWARD_ONLY. 


-- 
Bernt Marius Johnsen, Database Technology Group, 
Sun Microsystems, Trondheim, Norway

[jira] Commented: (DERBY-545) Should ResultSet Close implicitly?

Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
    [ 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/%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.


[jira] Updated: (DERBY-545) Should ResultSet Close implicitly?

Posted by "Philip Wilder (JIRA)" <de...@db.apache.org>.
     [ 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/%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

  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/%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


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/%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.
-
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


[jira] Closed: (DERBY-545) Should ResultSet Close implicitly?

Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
     [ 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: 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/%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.