At 05:44 p.m. 15/07/02 +0000, you wrote:

> > Is ther a way to change the default behavior of the default
> > transaction o to create multiple transactions per connection using
> > Java?
>
>Yes, you can go low level and use org.firebirdsql.jgds.GDS_Impl to
>talk to database server directly. API is very similar to one described
>in API Guide (it was adapted to Java, for example, if C code passes
>pointer + length, we pass only array of bytes). This code was created
>by Alejandro Alberola Arias and is the cornerstone of our driver.

Now I see things a lot clearer. I don't think I'd sacrifice the JDBC
advantages for multiple transactions per connection.
However I'm still interested in taking advantage of the different isolation
levels provided by Firebird as long as there's support for them in the JDBC
API.

If I do:
conn.setTransactionIsolation(Connection.TRANSACTION_SERIALIZABLE);
or
conn.setTransactionIsolation(Connection.TRANSACTION_READ_UNCOMMITTED);

Does the behavior of the transaction change?
If those methods are not there just to comply with the interface, I'd like
to see how do the 5 isolation levels present in JDBC map to the ones
provided in firebird/interbase.

I don't expect a lecture, just point me where to look if there's
documentatin on this.

Thanks.