| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | snpe <snpe(at)snpe(dot)co(dot)yu> |
| Cc: | Barry Lind <barry(at)xythos(dot)com>, "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 and |
| Date: | 2002-09-07 14:07:19 |
| Message-ID: | 200209071407.g87E7JF18173@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
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.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Elphick | 2002-09-07 15:33:18 | Re: Inheritance |
| Previous Message | Bruce Momjian | 2002-09-07 14:05:14 | Re: Making small bits of code available |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | snpe | 2002-09-07 18:57:55 | Re: [JDBC] problem with new autocommit config parameter and jdbc |
| Previous Message | snpe | 2002-09-07 12:59:31 | Re: [JDBC] problem with new autocommit config parameter and jdbc |