getTransactionIsolation() causes SQLException - unrecognized configuration parameter xactisolevel

Lists: pgsql-jdbc
From: Paul Marchant <pmarchant(at)gmail(dot)com>
To: pgsql-jdbc(at)postgresql(dot)org
Subject: getTransactionIsolation() causes SQLException - unrecognized configuration parameter xactisolevel
Date: 2005-04-04 23:04:48
Message-ID: 10c02a2505040416043f1e2ab1@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-jdbc

Setup: Postgres 8.0.1 & postgresql-8.0-310.jdbc3.jar

The following code:
---------------------------

try {
Class.forName("org.postgresql.Driver");
} catch (ClassNotFoundException e) {
System.out.println(e);
}

String url = "jdbc:postgresql://dbserver/test";
Properties p = new Properties();
p.setProperty("user", "test");
p.setProperty("password", "test");

Connection con;
try {
con = DriverManager.getConnection(url, p);
System.out.println("con.getTransactionIsolation() = " +
con.getTransactionIsolation());
con.close();
} catch (SQLException e) {
System.out.println(e);
}

Produces this:
---------------------
java.sql.SQLException: ERROR: unrecognized configuration parameter
"xactisolevel"

I've tried:
------------
1.) configuring the default_transaction_isolation parameter in postgresql.conf
2.) setting it programattically via con.setTransactionIsolation()

and now I'm stuck. I really don't care what the transaction isolation
level is. I'm trying to use Postgres 8.0 as a backend database for
Hibernate and org.postgresql.Driver.getTransactionIsolation() is
halting my progress.

Any help would be greatly appreciated.


From: Kris Jurka <books(at)ejurka(dot)com>
To: Paul Marchant <pmarchant(at)gmail(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: getTransactionIsolation() causes SQLException - unrecognized
Date: 2005-04-04 23:51:07
Message-ID: Pine.BSO.4.56.0504041846560.22117@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-jdbc

On Mon, 4 Apr 2005, Paul Marchant wrote:

> Setup: Postgres 8.0.1 & postgresql-8.0-310.jdbc3.jar
>
> con = DriverManager.getConnection(url, p);
> System.out.println("con.getTransactionIsolation() = " +
> con.getTransactionIsolation());
> con.close();
>
> Produces this:
> ---------------------
> java.sql.SQLException: ERROR: unrecognized configuration parameter
> "xactisolevel"

What's the complete stacktrace for this error? I'm not convinced it is a
JDBC driver problem.

Kris Jurka


From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: Paul Marchant <pmarchant(at)gmail(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: getTransactionIsolation() causes SQLException - unrecognized
Date: 2005-04-04 23:59:40
Message-ID: 4251D4EC.9070204@opencloud.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-jdbc

Paul Marchant wrote:
> Setup: Postgres 8.0.1 & postgresql-8.0-310.jdbc3.jar

> java.sql.SQLException: ERROR: unrecognized configuration parameter
> "xactisolevel"

I can't reproduce this against 8.0.0. 'xactisolevel' doesn't appear
anywhere in the current JDBC driver sources either (from memory it was
around in the 7.3 driver though).. Are you sure you are using the
driver version you think you are using?

Test code attached. I get this:

> $ java -cp .:postgresql-8.0-310.jdbc3.jar TestIso 'jdbc:postgresql://localhost:5800/test?user=oliver'
> driver version: PostgreSQL 8.0 JDBC3 with SSL (build 310)
> db version: 8.0.0
> con.getTransactionIsolation() = 2

-O

Attachment Content-Type Size
TestIso.java text/plain 788 bytes

From: Paul Marchant <pmarchant(at)gmail(dot)com>
To: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: getTransactionIsolation() causes SQLException - unrecognized configuration parameter xactisolevel
Date: 2005-04-05 18:08:37
Message-ID: 10c02a2505040511081e6d4d3d@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-jdbc

Thanks for the suggestions. I ran your code and it was a driver issue
after all. Eclipse was somehow finding a 7.3 version of driver on my
system. I have since expunged any files possible of causing the
conflict.