db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3304) Explicit commit inside a java procedure makes a dynamic result sets passed out unavailable
Date Thu, 28 Feb 2008 12:23:51 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573246#action_12573246

Knut Anders Hatlen commented on DERBY-3304:

Regarding isClosed() vs checkIfClose(), when you saw a test failing, was that before or after
the fix for DERBY-3404 was checked in? I had to change a couple of tests because they would
throw different exceptions with and without the fix (could change from connection closed to
result set closed), so it might be that it's a similar problem here. It sounds a bit strange
to me that we can return ResultSets where isClosed() returns false. But then perhaps the problem
is that appConn is null when this code is executed because the ownership for the ResultSet
is being transferred from the nested connection to the top-level connection?

Anyway, it's not that many code lines extra, so don't spend too much energy on it. Thanks
for checking it out and addressing my other comments.

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

View raw message