[
https://issues.apache.org/jira/browse/DERBY-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561582#action_12561582
]
Mamta A. Satoor commented on DERBY-3304:
----------------------------------------
Sorry for misinterpreting your comment, Dag. You are right, in this specific
test case, where there is a commit inside the java stored procedure, close is
getting called on CallStatementResultSet which is just getting opened. I think
work on DERBY-3037 will help resolve this issue too. In DERBY-3037, we have an
example of Java Stored routine which is a function, which also does a commit
inside it. And that commit causes the resultset that will be returned by the
function to close. I am hoping to get some pointers on how to recognize which
resultsets should be closed and which should be left often.
> 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
> 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.
