Subject Re: [Firebird-Java] Difference between 1.5.5 an 2.1.1 and ResultSets in autocommit connections
Author Aljoscha Rittner
Hi Roman!

>> With 1.5.5 this works for me, but with 2.1.1 the result set from stmt1
>> get closed. I think the default ResultSetHoldability is changed
>> between the versions (from HOLD_CURSORS_OVER_COMMIT in 1.5.5 to
>> CLOSE_CURSORS_AT_COMMIT in 2.1.1). Is this right?
> Nope. The reasons are described in the release notes and this effect is
> visible only in auto-commit mode.

Ok I found the info in the relese notes.

>> And: Is this ok?
> Yes. But better switch the auto-commit off - in auto-commit mode and
> with scrollable result set, everything is fetched to the client and kept
> in memory.

I've no way to change this design in my application. The app has
thousands "select and forget" statements with deep loops in different

But the prepareStatement is in a central wrapper, easy to change. Only
the source code compatibility is a problem. It should work with Java 1.4
and 1.5 (and jaybird 1.5.x and 2.x) - so I need reflection and a
driver version test. :-/

Thank you for your help and best regards,