At 22:59 05/12/2002 -0000, you wrote:

>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.

I'm really new to this stuff - I'm just learning Java, and this is my first
post to the list, but I think that b is a *really* bad idea. In my
application, if you commit a transaction at the wrong time, a lot of things
get totally screwed up. I think that if there is a transaction in progress
when you try to set an isolation level, it should probably throw an
exception. You should't attempt this. I think I'd rather it rolled back
than committed. If the spec says "you can wait until the next transaction
before making the isolation level change", which you implied in an earlier
post, then I'd definately do that.

Robert Munro
--
Robert (Jamie) Munro - IT department
Viva Network - Helping 'children at risk'
by linking & enhancing the Christian Response
http://www.viva.org/
PO Box 633, Oxford, England, OX2 0XZ
Tel : +44 1865 320131 Switchboard : +44 1865 320 100