db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dag.Wan...@Sun.COM (Dag H. Wanvik)
Subject Re: [jira] Commented: (DERBY-3304) Explicit commit inside a java procedure makes a dynamic result sets passed out unavailable
Date Fri, 25 Jan 2008 13:53:25 GMT
"Mamta A. Satoor (JIRA)" <jira@apache.org> writes:

>     [ 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. 

No problem :-) I should have been more explicit. Would be nice to get rid
of this; like Dan said, it can be confusing..

Dag

> 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.

Mime
View raw message