[
https://issues.apache.org/jira/browse/DERBY-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568817#action_12568817
]
Mamta A. Satoor commented on DERBY-3304:
----------------------------------------
Added a junit test case for number of code changes for transaction ending time
that went in as part of DERBY-3304. This new test will check those code changes
for specific case of rollback inside a java procedure call. The test went into
trunk(revision 627673) and 10.3 codeline(revision 627674).
The test case runs in embedded mode to show the correct behavior for rollback
inside a java procedure causing all the resultsets to close. The test case for
now has been commented out for network server mode and it should be enabled
when DERBY-3414 is fixed. The reason for network server test disability is that
rollback inside the procedure does not close all the resultsets in Network
server mode.
> 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.
