Re: Transactions within a function body - Mailing list pgsql-general

From Reg Me Please
Subject Re: Transactions within a function body
Date
Msg-id 200810021625.19719.regmeplease@gmail.com
Whole thread Raw
In response to Re: Transactions within a function body  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Transactions within a function body  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-general
Il Thursday 02 October 2008 16:15:10 Alvaro Herrera ha scritto:
> Reg Me Please escribió:
> > Well, if it is a limitation, and having it would lead to a "better
> > product", why not making it a feature for the next still-open release?
>
> Because no one is working on implementing it?
>
> > In my opinion that's more than a limitation, it's a missing feature.
> > In your code you often need to create savepoints to delay the decision
> > for the commitment.
> > A Pl/PgSQL function is just a bunch of code you want to move into the DB.
> > So the need for savepoints seems to me to be still there.
>
> You can nest blocks arbitrarily, giving you the chance to selectively
> rollback pieces of the function.  It's only a bit more awkward.

You mean I can issue a ROLLBACK command within a BEGIN...END; block to roll it
back?

pgsql-general by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Transactions within a function body
Next
From: "Matthew Terenzio"
Date:
Subject: tsearch2 query