> This is just an unfortunately the way the driver implements auto
> commit mode - I don't know exactly why but it was necessary (at
> least as far as anyone could see) to do this to implement
> auto-commit with firebird.

Reason for this is that server supports auto-commit mode using commit
retaining (what this is you can read in documentation and ask in
Firebird-Support group). Unfortunatelly commit retaining might inhibit
garbage collection and after some point will cause an error "maximum
number of savepoints exceeded". So, fetching all data to the client
seemed for us the only option to implement auto-commit mode cleanly.

There might be clever solution, so volunteers welcome.

You should not rely on the fact that result set will be cached on the
client. This is not specified in the standard and most likely no other
driver do this.

Best regards,
Roman Rokytskyy