Re: [JDBC] problem with new autocommit config parameter

From: Barry Lind <barry(at)xythos(dot)com>
To: snpe <snpe(at)snpe(dot)co(dot)yu>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [JDBC] problem with new autocommit config parameter
Date: 2002-09-07 22:39:46
Message-ID: 3D7A8032.4010706@xythos.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-jdbc

Yes it is possible, but according to the jdbc spec, a new connection in
jdbc is always initialized to autocommit=true. So jdbc needs to ignore
whatever the current server setting is and reset to autocommit=true.

--Barry

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 ?
>
>
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ajay Ayyagari 2002-09-07 22:54:32 Mac OS X 10.2/Darwin 6.0
Previous Message Bruce Momjian 2002-09-07 22:09:34 Testing for failures in configure.in

Browse pgsql-jdbc by date

  From Date Subject
Next Message snpe 2002-09-07 23:27:19 Re: [HACKERS] problem with new autocommit config parameter
Previous Message snpe 2002-09-07 20:09:45 Re: [JDBC] problem with new autocommit config parameter