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

From snpe
Subject Re: [JDBC] problem with new autocommit config parameter and jdbc
Date
Msg-id 200209072057.55317.snpe@snpe.co.yu
Whole thread Raw
In response to Re: [JDBC] problem with new autocommit config parameter and  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
On Saturday 07 September 2002 04:07 pm, Bruce Momjian wrote:
> snpe wrote:
> > 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 ?
>
> Sure, you can do SHOW autocommit.
I am interesting with JDBC driver.
When I make connection in base I want that driver find autocommit mode 
(from postgresql.conf or call in backend) and set mode true or false 

thanks



pgsql-hackers by date:

Previous
From: Joe Conway
Date:
Subject: Re: About connectby()
Next
From: Alvaro Herrera
Date:
Subject: current_schemas()