| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | " Rodríguez =?iso-8859-15?q?_Rodr=EDguez?=, Pere" <prr(at)hosppal(dot)es> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: nested transaction |
| Date: | 2004-08-10 12:34:54 |
| Message-ID: | 200408101434.54703.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Am Dienstag, 10. August 2004 13:30 schrieb "Rodríguez Rodríguez, Pere":
> For example, I have a pA procedure that update some data, so this procedure
> execute a begin, after manipulate data and ends with commit/rollback. pA
> procedure can to be called directly by the client aplication. In other
> hand, I have a pB procedure that also update some data and calls pA
> procedure, so pB procedure execute a begin, after manipulate data, after
> call pA procedure and ends with commit/rollback. pB procedure can also to
> be called directly by the client aplication.
>
> The problem is that pA procedure can't do a new transaction, so what can I
> do?
Use savepoints all the time.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Olivier Guilyardi | 2004-08-10 12:35:47 | Re: Listing views |
| Previous Message | Olivier Guilyardi | 2004-08-10 11:54:59 | Re: Listing views |