| From: | Gregory Wood <gwood(at)ewebengine(dot)com> |
|---|---|
| To: | Martin Marques <martin(at)bugs(dot)unl(dot)edu(dot)ar> |
| Cc: | Richard Huxton <dev(at)archonet(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: transactions in plpgsql |
| Date: | 2004-03-20 19:36:06 |
| Message-ID: | 405C9D26.5070207@ewebengine.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> El Vie 19 Mar 2004 12:49, Richard Huxton escribió:
>
>>On Friday 19 March 2004 13:01, Martin Marques wrote:
>>
>>>I'm building some functions in plpgsql, and I got to a point where I
>>>thought: How are transactions used in the function? Is it posible to
>>>rollback the modifications that were made to the tables at some point in
>>>the plpgsql function?
>>
>>You can abort the entire transaction by raising an exception. Nothing more
>>sophisticated is available at the moment.
>
> OK, this would mean that the whole function is in a transaction. But what if I
> call another function from within this one and it that function gets an error
> which is RAISED? Can I do something about it on the original function, or do
> I have to let it all rollback?
Until nested transactions are in place (7.5 maybe?), it all has to rollback.
Greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Garamond | 2004-03-20 19:44:26 | Re: Index selection (and partial index) for BYTEA field |
| Previous Message | Gregory Wood | 2004-03-20 19:33:55 | Re: Triggers After INSERT |