Hi,

I have changed transaction behavior on my computer and I'm ready to
commit. All test cases succeeded (except TestFBDriver.testWarnings(),
I will check if this is a Linux/CS specific issue). My changes were:

a) no transaction is started right after commit/rollback;
b) setTransactionIsolation() calls commit and then modifies TPB;
c) TRANSACTION_NONE and TRANSACTION_READ_UNCOMMITTED are not supported
and are promoted to TRANSACTION_READ_COMMITTED.

Also there are one place where I'm not sure what to do:
setAutoCommit() commits transaction before changing the auto-commit
value, and later starts a new transaction if new mode is not
auto-commit. Do you have any ideas if this is correct or not?

If nobody has any objection to my changes I will commit them into the
CVS tomorrow in the evening (~22:00 UTC).

Also I was not able to find any place in the code where statement
handle is deallocated in commit or rollback. The only thing I found
was that we close result sets (isc_dsql_free_statemet() with
DSQL_close option) in commit or rollback. And I think this is correct
behavior.

If I missed something, please provide a test case or at least an
execution path that can lead to deallocating statement on transaction end.


Best regards,
Roman Rokytskyy