Submitted by: @mrotteveel

Is related to JDBC307

The fix for JDBC307 goes through a number of layers to not close the serverside cursor on commit/rollback (as this is done automatically by Firebird). It might be worthwhile to investigate an alternative solution, where the signalling of commiting or rolling back will make those resources (result set, but also blobs) switch to closed state without calling the server side.

This would probably be cleaner and less confusing.