| From: | snpe <snpe(at)snpe(dot)co(dot)yu> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Barry Lind <barry(at)xythos(dot)com> |
| Cc: | "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 jdbc |
| Date: | 2002-09-07 12:59:31 |
| Message-ID: | 200209071459.31227.snpe@snpe.co.yu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers 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 ?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-09-07 14:05:14 | Re: Making small bits of code available |
| Previous Message | Masaru Sugawara | 2002-09-07 12:41:43 | About connectby() |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-09-07 14:07:19 | Re: [JDBC] problem with new autocommit config parameter and |
| Previous Message | Bruce Momjian | 2002-09-07 00:55:17 | Re: problem with new autocommit config parameter and jdbc |