[
https://issues.apache.org/jira/browse/DERBY-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572374#action_12572374
]
mamtas edited comment on DERBY-3304 at 2/26/08 9:28 AM:
-----------------------------------------------------------------
Before addressing Knut's comments, I wanted to commit changes that were already
in my codeline. The changes went in as revision 631108 into trunk. These
changes ensured that when an exception is raised, the rollback caused by it
will cleanup CallableStatementResultset such that all the resultsets associated
with it are closed and CallableStatementResultset is available for reuse during
next execution. More info can be found in commit comments.
Next, I will work on migrating these changes into 10.3 codeline and addressing
Knut's comments on revision 629926.
was (Author: mamtas):
Before addressing Knut's comments, I wanted to commit changes that were
already in my codeline. The changes went in as revision 63110 into trunk. These
changes ensured that when an exception is raised, the rollback caused by it
will cleanup CallableStatementResultset such that all the resultsets associated
with it are closed and CallableStatementResultset is available for reuse during
next execution. More info can be found in commit comments.
Next, I will work on migrating these changes into 10.3 codeline and addressing
Knut's comments on revision 629926.
> 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.
