[
https://issues.apache.org/jira/browse/DERBY-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571144#action_12571144
]
Mamta A. Satoor commented on DERBY-3304:
----------------------------------------
I just finished making code changes and added a test case with revision 629926.
These code changes ensure that a user initiated rollback through JDBC
Connection object will not close the resultsets that do not return rows. More
detailed info on the patch can be found through the commit comments for 629926.
As next 2 tasks, I will merge these changes into 10.3 codeline and I will work
on the case where a rollback is caused because of an exception. In such a case,
we should close all the resultsets no matter if they return rows or not.
> Explicit commit inside a java procedure makes a dynamic result sets passed
> out unavailable
> ------------------------------------------------------------------------------------------
>
> Key: DERBY-3304
> URL: https://issues.apache.org/jira/browse/DERBY-3304
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.4.0.0
> Reporter: Daniel John Debrunner
> Assignee: Mamta A. Satoor
> Attachments: Main.java
>
>
> Repro (Main.java) that shows changed behavior after svn 602991
> (the patch committed for this issue). It seems a regression: (originally from
> Dag H. Wanvik attached to DERBY-1585)
> An explicit commit inside a stored procedure makes a dynamic result sets
> passed out unavailable, even if the commit is executed *prior* to the result
> set; as in the repro.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
