[ https://issues.apache.org/jira/browse/DERBY-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565649#action_12565649 ]
Mamta A. Satoor commented on DERBY-3304: ---------------------------------------- I agree that Activation.reset should be able to just close the resultset associated with it without having to look at holdability or returnsRows() method. This functionality of looking at holdability and returnsRows should be implemented separately. I will work on cleaning up code for Activation.reset and putting the functionality required by commit in the appropriate method. > 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.