| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: autocommit in 7.4 |
| Date: | 2003-07-31 14:26:42 |
| Message-ID: | 200307311426.h6VEQgP17293@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > The issue I have is that every interface that relies on libpq is going
> > to have to code it itself. Is that OK?
>
> So? Most interfaces have to adhere to their own notions of transaction
> semantics and control API anyway. libpq should stay out of their way
> rather than try to be helpful. I see this as not different from the
> lesson we learned that doing it in the backend isn't the right place.
I know Perl and jdbc do, but things like c++ and libpgeasy don't really
have a specification to follow. With the ability to check the
transaction status, it might now be easy enough to do autocommit that
having it happen in every interfaces will be ok.
--
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 | Bruce Momjian | 2003-07-31 14:43:00 | Re: patch queue |
| Previous Message | Tom Lane | 2003-07-31 14:14:59 | Re: how to dump all tables with pg_dump ? |