| From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
|---|---|
| To: | Mario Weilguni <mweilguni(at)sime(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org> |
| Subject: | Re: BEGIN inside transaction should be an error |
| Date: | 2006-05-10 09:44:39 |
| Message-ID: | 0517D06E325F2EBDBF814E58@[172.26.14.230] |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
--On Mittwoch, Mai 10, 2006 10:14:22 +0200 Mario Weilguni
<mweilguni(at)sime(dot)com> wrote:
> No, I want that there is a setting or GUC that controls whether an error
> or a warning is raised when "begin" is executed within a transaction. I
> know of several php database wrappers that will be seriously broken when
> errors are raised...
Such a behavior is already broken by design. I think it's not desirable to
blindly do
transaction start or commit without tracking the current transaction state.
So these wrappers
need to be fixed first.
--
Bernd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mario Weilguni | 2006-05-10 10:31:52 | Re: BEGIN inside transaction should be an error |
| Previous Message | Peter Eisentraut | 2006-05-10 08:59:51 | Re: BEGIN inside transaction should be an error |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mario Weilguni | 2006-05-10 10:31:52 | Re: BEGIN inside transaction should be an error |
| Previous Message | Peter Eisentraut | 2006-05-10 08:59:51 | Re: BEGIN inside transaction should be an error |