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 "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2012/09/11 17:29:07 UTC

[jira] [Created] (DERBY-5921) Result sets opened before a savepoint could be left open when the savepoint is rolled back

Dag H. Wanvik created DERBY-5921:
------------------------------------

             Summary: Result sets opened before a savepoint could be left open when the savepoint is rolled back
                 Key: DERBY-5921
                 URL: https://issues.apache.org/jira/browse/DERBY-5921
             Project: Derby
          Issue Type: Improvement
          Components: JDBC, SQL
            Reporter: Dag H. Wanvik


Cf discussion on DERBY-5545 with John Hendikx.

Quote from SQL standard:

In section 16.7 <rollback statement>, section General Rule 3) <savepoint specified>, clause g) reads:

"For every open cursor CR in any SQL-client module associated with the current SQL-transaction that
was opened subsequent to the establishment of S, the following statement is implicitly executed:
CLOSE CR"

I take that to mean that the cursor should remain open iff it was established prior to the savepoint, and, by analogy, the JDBC result set should stay open too.

and clause h):

"The status of any open cursors in any SQL-client module associated with the current SQL-transaction
that were opened by the current SQL-transaction before the establishment of S is implementation defined. "

We could allow result sets to stay open since the current behavior closing them maybe be unexpected for users, cf. DERBY-5545.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (DERBY-5921) Result sets opened before a savepoint could be left open when the savepoint is rolled back

Posted by "Mamta A. Satoor (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-5921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mamta A. Satoor updated DERBY-5921:
-----------------------------------

    Issue & fix info: Repro attached
             Urgency: Normal
              Labels: derby_triage10_10  (was: )
    
> Result sets opened before a savepoint could be left open when the savepoint is rolled back
> ------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5921
>                 URL: https://issues.apache.org/jira/browse/DERBY-5921
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC, SQL
>            Reporter: Dag H. Wanvik
>              Labels: derby_triage10_10
>         Attachments: Derby5921.java
>
>
> Cf discussion on DERBY-5545 with John Hendikx.
> Quote from SQL standard:
> In section 16.7 <rollback statement>, section General Rule 3) <savepoint specified>, clause g) reads:
> "For every open cursor CR in any SQL-client module associated with the current SQL-transaction that
> was opened subsequent to the establishment of S, the following statement is implicitly executed:
> CLOSE CR"
> I take that to mean that the cursor should remain open iff it was established prior to the savepoint, and, by analogy, the JDBC result set should stay open too.
> and clause h):
> "The status of any open cursors in any SQL-client module associated with the current SQL-transaction
> that were opened by the current SQL-transaction before the establishment of S is implementation defined. "
> We could allow result sets to stay open since the current behavior closing them maybe be unexpected for users, cf. DERBY-5545.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (DERBY-5921) Result sets opened before a savepoint could be left open when the savepoint is rolled back

Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-5921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dag H. Wanvik updated DERBY-5921:
---------------------------------

    Attachment: Derby5921.java

Uploading a repro, "Derby5921.java".
                
> Result sets opened before a savepoint could be left open when the savepoint is rolled back
> ------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5921
>                 URL: https://issues.apache.org/jira/browse/DERBY-5921
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC, SQL
>            Reporter: Dag H. Wanvik
>         Attachments: Derby5921.java
>
>
> Cf discussion on DERBY-5545 with John Hendikx.
> Quote from SQL standard:
> In section 16.7 <rollback statement>, section General Rule 3) <savepoint specified>, clause g) reads:
> "For every open cursor CR in any SQL-client module associated with the current SQL-transaction that
> was opened subsequent to the establishment of S, the following statement is implicitly executed:
> CLOSE CR"
> I take that to mean that the cursor should remain open iff it was established prior to the savepoint, and, by analogy, the JDBC result set should stay open too.
> and clause h):
> "The status of any open cursors in any SQL-client module associated with the current SQL-transaction
> that were opened by the current SQL-transaction before the establishment of S is implementation defined. "
> We could allow result sets to stay open since the current behavior closing them maybe be unexpected for users, cf. DERBY-5545.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira