Evgeney,

> Bun I Have problem after call commit, i have closed ResultSet.
> Is it requirement JDBC? I think it specific realisation bridge
> to FB. To resolve Any realisation RDBM, FB have specific tools.
> For example transaction isolations.

Correct me if I am wrong, but result set cannot survive transaction
end (either isc_commit_transaction or isc_rollback_transaction), can
it?

There is no requirement that ResultSet is closed on Connection.commit
(), only that ResultSet is closed when corresponding Statement is
closed. But, since FB closes result set anyway (see description of
isc_commit_transaction), there is no point to keep FBResultSet open.

JDBC specification requires us to end transaction. And we do this by
using isc_commit_transaction and isc_rollback_transaction and not
isc_commit_retaining. This third option has no corresponding method
in JDBC.

> What i do. But Java not support multiple inheritance realization.
> And I must local putch code or write copies code.

I personally believe that multiple inheritance is evil thing, but
probably I just to Jav-ish. Anyway, if you have any suggestions how
our object-oriented model can be improved, provide your suggestions.
There will be no change before release, but after it we are free to
change driver model.

Best regards,
Roman Rokytskyy