Re: plpgsql and INSERT/UPDATE/DELETE RETURNING - Mailing list pgsql-hackers

From Jim C. Nasby
Subject Re: plpgsql and INSERT/UPDATE/DELETE RETURNING
Date
Msg-id 20060814151958.GC27928@pervasive.com
Whole thread Raw
In response to plpgsql and INSERT/UPDATE/DELETE RETURNING  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: plpgsql and INSERT/UPDATE/DELETE RETURNING
List pgsql-hackers
On Sun, Aug 13, 2006 at 03:54:18PM -0400, Tom Lane wrote:
> which is that you can use aggregate functions in the RETURNING list and
> get a single-row result that is aggregated across all affected rows.
> It's too late to consider implementing that for 8.2, I fear, but I think
> maybe we should put it on the TODO list for later.

Aggregates sound interesting, though I'm not sure how useful they'd
actually be. I think something like

FOR v_row IN (UPDATE ... RETURNING ...)

would be a lot more useful (if it's not already in the patch).
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461


pgsql-hackers by date:

Previous
From: Perez
Date:
Subject: Re: An Idea for planner hints
Next
From: "Jim C. Nasby"
Date:
Subject: Re: problem with volatile functions in subselects ?