BUG #1251: setTransactionIsolation does not seem to work - Mailing list pgsql-bugs

From PostgreSQL Bugs List
Subject BUG #1251: setTransactionIsolation does not seem to work
Date
Msg-id 20040913104303.20A215A10AF@www.postgresql.com
Whole thread Raw
Responses Re: BUG #1251: setTransactionIsolation does not seem to work  (Kris Jurka <books@ejurka.com>)
List pgsql-bugs
The following bug has been logged online:

Bug reference:      1251
Logged by:          Fernando Bellas

Email address:      fbellas@udc.es

PostgreSQL version: 7.4.3

Operating system:   Red Hat 7.1

Description:        setTransactionIsolation does not seem to work

Details:

Hi,

First of all, the version I am using of PostgreSQL is 7.4.5, and *not* 7.4.3
(I have set 7.4.3 in the form, since it does not allow to choose 7.4.5).

I have tested several JDBC drivers (pg74.213.jdbc3.jar, pg74.215.jdbc3.jar,
pg74.213.jdbc2.jar and pg74.213.jdbc2ee.jar), and
connection.setTransactionIsolation does not change the transaction isolation
level (maybe the problem is with the database and not with the JDBC driver).

The following code prints "2" (TRANSACTION_READ_COMMITED) as the value of
the transaction isolation levels.

connection.setAutoCommit(false);
int oldTransactionIsolation =
  connection.getTransactionIsolation();
System.out.println("oldTransactionIsolation = " +
     oldTransactionIsolation);
connection.setTransactionIsolation(
    Connection.TRANSACTION_SERIALIZABLE);
System.out.println("newTransactionIsolation = " +
    connection.getTransactionIsolation());

Thanks in advance!
Fernando.

pgsql-bugs by date:

Previous
From: Kris Jurka
Date:
Subject: Re: BUG #1233: JDBC driver: moveToCurrentRow fails
Next
From: Rafael Martinez Guerrero
Date:
Subject: Re: PosgreSQL is crashing with a signal 11 - Bug?