| From: | Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl> |
|---|---|
| To: | David Johnston <polobo(at)yahoo(dot)com> |
| Cc: | "'Andre Lopes'" <lopes80andre(at)gmail(dot)com>, "'postgresql Forums'" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Transactions and ID's generated by triggers |
| Date: | 2011-02-28 19:00:30 |
| Message-ID: | 01F0EC32-7105-4B18-A06D-B6DE904CB4EC@solfertje.student.utwente.nl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 28 Feb 2011, at 24:37, David Johnston wrote:
> Using pl/pgsql you can:
You don't need pl/pgsql for that. You can return the resultset of the first insert into a client-side variable (while still making use of the RETURNING-clause of course).
Of course, the benefit of using pl/pgsql for this is that you could make the desired behaviour independent of client-implementations (which are all too likely to differ if there are multiple types of clients). However, for that to work reliably you will need to do some extra work to make sure it's the only possible code-path for inserting those records.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4d6bf0da235882099214672!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | suresh ramasamy | 2011-02-28 19:10:35 | dear friend |
| Previous Message | Andrew Sullivan | 2011-02-28 18:10:19 | Re: Lock ACCESS EXCLUSIVE and Select question ! |