Hello

At 05/12/2002 15:21 +0000, you wrote:

>> There is a NPE when using setTransactionIsolation
>> (Connection.TRANSACTION_READ_UNCOMMITED).
>>
>> It seems TRANSACTION_READ_UNCOMMITED is lost in FBTpbMapper
>> constructor and isc_tpb_mapping.properties
>
>Hmm... it should throw an SQLException. I think we do not support
>read uncommitted. Is there any TPB combination that can provide "read
>uncommitted" semantics?

Until the changes, if the transaction isolation level requested is read_uncommited, not supported by FB, then the driver apply the specification, and set the transaction isolation level to read_commited. You can see this in setTransactionIsolation in FBTpb version 1.6 and previous.

JDBC 3.0 specification
If a driver does not support the transactionIsolation level specified in an invocation to setTransactionIsolation, it is allowed to substitute a higher, more restrictive transaction isolation level. If a driver is unable to substitute a higher transaction level, it throws a SQLException (jdbc3.0 10.2.1)

You can also set the level to read_commited inside the setTransactionIsolation method.

Best Regards
Blas Rodriguez Somoza.