[DERBY-3037] Language ResultSet.finish() is called even when the ResultSet is going to be re-used.

• Type: Bug
• Status: Reopened
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.4.1.3
• Fix Version/s: 10.3.3.1
• Component/s: SQL
• Urgency: Normal
• Issue & fix info: Repro attached
• Assignee: Unassigned
• Reporter: Daniel John Debrunner
• Created: 31/Aug/07 23:40
• Updated: 17/Apr/13 19:10

Description

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.

Issue Links

• relates to: DERBY-827 Performance can be improved by re-using language ResultSets across Activation executions.