Re: SQL functions, INSERT/UPDATE/DELETE RETURNING, and triggers

On 10/12/06, Tom Lane <tgl@sss.pgh.pa.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@enterprisedb.com
Iselin, New Jersey 08830            | http://www.enterprisedb.com/