Re: [HACKERS] problem with new autocommit config parameter and jdbc - Mailing list pgsql-jdbc

From snpe
Subject Re: [HACKERS] problem with new autocommit config parameter and jdbc
Date
Msg-id 200209071459.31227.snpe@snpe.co.yu
Whole thread Raw
In response to Re: [HACKERS] problem with new autocommit config parameter and jdbc  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: [HACKERS] problem with new autocommit config parameter and  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-jdbc
On Saturday 07 September 2002 02:55 am, Bruce Momjian wrote:
> Barry Lind wrote:
> > Haris,
> >
> > You can't use jdbc (and probably most other postgres clients) with
> > autocommit in postgresql.conf turned off.
> >
> > Hackers,
> >
> > How should client interfaces handle this new autocommit feature?  Is it
> > best to just issue a set at the beginning of the connection to ensure
> > that it is always on?
>
> Yes, I thought that was the best fix for apps that can't deal with
> autocommit being off.
Can client get information from backend for autocommit (on or off) and that
work like psql ?



pgsql-jdbc by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] problem with new autocommit config parameter and jdbc
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] problem with new autocommit config parameter and