| From: | Curt Sampson <cjs(at)cynic(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, 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 |
| Date: | 2002-09-10 02:59:55 |
| Message-ID: | Pine.NEB.4.44.0209101158440.13186-100000@angelic.cynic.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
On Mon, 9 Sep 2002, Tom Lane wrote:
> If autocommit=off really seriously breaks JDBC then I don't think a
> simple SET command at the start of a session is going to do that much
> to improve robustness. What if the user issues another SET to turn it
> on?
You mean, to turn it off again? The driver should catch this, in theory.
In practice we could probably live with saying, "Don't use SET
AUTOCOMMIT; use the methods on the Connection class instead."
Probably the driver should be changed for 7.3 just to use the server's
SET AUTOCOMMIT functionality....
cjs
--
Curt Sampson <cjs(at)cynic(dot)net> +81 90 7737 2974 http://www.netbsd.org
Don't you know, in this new Dark Age, we're all light. --XTC
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sean Chittenden | 2002-09-10 03:02:19 | Re: Optimization levels when compiling PostgreSQL... |
| Previous Message | Bruce Momjian | 2002-09-10 02:59:18 | Re: Optimization levels when compiling PostgreSQL... |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-09-10 03:27:13 | Re: [JDBC] problem with new autocommit config parameter and jdbc |
| Previous Message | Curt Sampson | 2002-09-10 02:51:21 | Re: problem with new autocommit config parameter and jdbc |