| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | pg(at)fastcrypt(dot)com |
| Cc: | Barry Lind <blind(at)xythos(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: When running with autocommit false only the first BEGIN |
| Date: | 2004-11-23 12:18:05 |
| Message-ID: | 41A32A7D.2010102@opencloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Dave Cramer wrote:
> That certainly doesn't seem acceptable. As Barry points out people will
> really be in the dark when their code doesn't work.
There's nothing much the driver can do about it other than not using the
new features of V3. This needs a server-side fix.
We could make BEGIN/COMMIT/ROLLBACK more visible at the (small) cost of
an extra Parse on each execution. But you're still going to have the
same problem with user queries once statements start using server-side
prepare.
See http://archives.postgresql.org/pgsql-hackers/2004-05/msg01173.php
for past discussion. I looked at fixing it briefly but didn't have time
to put together a patch.
-O
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vadim Nasardinov | 2004-11-23 14:25:30 | better logging on the backend (was: Re: When running with autocommit false only the first BEGIN) |
| Previous Message | Dave Cramer | 2004-11-23 12:04:50 | Re: When running with autocommit false only the first BEGIN |