[ http://issues.apache.org/jira/browse/DERBY-1208?page=comments#action_12419923 ]
Daniel John Debrunner commented on DERBY-1208: ---------------------------------------------- I'm not sure this is the correct approach, but I need to investigate more. Typically (I think) we don't have finally blocks in the language ResultSet classes that close other ResultSets. I think this is handled at a higher level by closing the entire ResultSet tree. The patch is useful in that it points out the issue and provides a test. It potentially indicates that there is an issue with close methods for the two modified ResultSet implementations, e.g. the closeSource method in GroupedAggregateResultSet has one path where the source ResultSet is not closed, that logic looks strange. > Attempts to reuse a prepared statement after an execution-time error causes > ASSERT failure in SANE mode, but work fine in INSANE. > --------------------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-1208 > URL: http://issues.apache.org/jira/browse/DERBY-1208 > Project: Derby > Type: Bug > Components: JDBC > Versions: 10.2.0.0 > Reporter: A B > Priority: Minor > Attachments: 1208.diff, d1208.java, derby.log > > Please see the comments in DERBY-1196 for the discussion that prompted the > filing of this issue. In short, if one attempts to reuse a prepared > statement with a new set of parameters after a previous call to execute that > statement has failed, the result will be an ASSERT failure in SANE mode. > When the same thing is done in INSANE mode, everything works as one might > expect it to. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
