[ https://issues.apache.org/jira/browse/DERBY-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553877 ]
Mamta A. Satoor commented on DERBY-3037: ---------------------------------------- ommited the patch Derby_3037_AlterTableConstantActionChanges_v1_diff.txt with revision 606106 into trunk. Will merge into 10.3 later. > Language ResultSet.finish() is called even when the ResultSet is going to be > re-used. > ------------------------------------------------------------------------------------- > > Key: DERBY-3037 > URL: https://issues.apache.org/jira/browse/DERBY-3037 > Project: Derby > Issue Type: Bug > Components: SQL > Affects Versions: 10.4.0.0 > Reporter: Daniel John Debrunner > Assignee: Mamta A. Satoor > Fix For: 10.3.2.2, 10.4.0.0 > > Attachments: Derby_3037_AlterTableConstantActionChanges_v1_diff.txt, > Derby_3037_AlterTableConstantActionChanges_v1_stat.txt > > > DERBY-827 (correctly) changed the lifetime of the language ResultSet tree to > be the lifetime of the activation, but did not fix up the correct calls to > ResultSet.close() and ResultSet.finish(). > A language ResultSet's lifetime should be driven by the activation, so > activation.close() should call finish() on its ResultSet. > EmbedResultSet should call close on its language ResultSet (theResults field) > when the JDBC ResultSet is closed, it should not be calling finish() on its > ResultSet. > See comments in DERBY-827 for some more details and issues. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.