| From: | Mario Weilguni <mweilguni(at)sime(dot)com> |
|---|---|
| To: | Bernd Helmle <mailings(at)oopsware(dot)de> |
| 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 10:36:07 |
| Message-ID: | 200605101236.07403.mweilguni@sime.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Am Mittwoch, 10. Mai 2006 11:44 schrieb Bernd Helmle:
> --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.
You mean broken like "transform_null_equals"? Or "add_missing_from"?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2006-05-10 12:01:18 | Re: [GENERAL] intarray internals |
| Previous Message | Mario Weilguni | 2006-05-10 10:31:52 | Re: BEGIN inside transaction should be an error |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bernd Helmle | 2006-05-10 13:01:45 | Re: BEGIN inside transaction should be an error |
| Previous Message | Mario Weilguni | 2006-05-10 10:31:52 | Re: BEGIN inside transaction should be an error |