Re: SET AUTOCOMMIT TO OFF no longer supported

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Carlos Correia <carlos(at)m16e(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: SET AUTOCOMMIT TO OFF no longer supported
Date: 2006-02-04 19:29:23
Message-ID: 20785.1139081363@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Carlos Correia <carlos(at)m16e(dot)com> writes:
> Tom Lane escreveu:
> | I think you need a newer JDBC driver. (If the app itself, rather than
> | the driver, is trying to issue this command then the app is so broken
> | it doesn't deserve to live.)

> newer then this:
> http://jdbc.postgresql.org/download/postgresql-8.1-404.jdbc3.jar?

No, that driver is plenty new enough to know not to do this. It's the
app that's broken, then --- it has no business messing with SET
AUTOCOMMIT rather than using the JDBC-spec methods to control
transaction boundaries.

> | It might have worked with 7.3, but 7.4 would give this same error message.

> Well, as I said before, it's been working perfectly from several years
> with 7.4.

Interesting. Maybe the app is coded to use SET AUTOCOMMIT only with 7.3
(which is the *only* PG release series that ever had this command),
but its version test is broken so that it tries to use it with 8.*?

regards, tom lane

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Carlos Correia 2006-02-04 19:39:44 Re: SET AUTOCOMMIT TO OFF no longer supported
Previous Message Carlos Correia 2006-02-04 19:15:16 Re: SET AUTOCOMMIT TO OFF no longer supported