| From: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: SQL functions, INSERT/UPDATE/DELETE RETURNING, and triggers |
| Date: | 2006-10-12 18:37:46 |
| Message-ID: | 36e682920610121137j35263d23pd8b9a9f5710dd103@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/12/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I think the most promising answer may be to push RETURNING rows into a
> TupleStore and then read them out from there, which is pretty much the
> same approach we adopted for RETURNING queries inside portals.
It certainly sounds like the safest implementation and I can't think
of any simple way around using a tuplestore in this type of case.
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation | fax: 732.331.1301
33 Wood Ave S, 2nd Floor | jharris(at)enterprisedb(dot)com
Iselin, New Jersey 08830 | http://www.enterprisedb.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2006-10-12 18:44:05 | Re: SQL functions, INSERT/UPDATE/DELETE RETURNING, and triggers |
| Previous Message | Jim C. Nasby | 2006-10-12 18:28:18 | Re: SQL functions, INSERT/UPDATE/DELETE RETURNING, and triggers |