Re: plpgsql and INSERT/UPDATE/DELETE RETURNING
От | Jim C. Nasby |
---|---|
Тема | Re: plpgsql and INSERT/UPDATE/DELETE RETURNING |
Дата | |
Msg-id | 20060814151958.GC27928@pervasive.com обсуждение исходный текст |
Ответ на | plpgsql and INSERT/UPDATE/DELETE RETURNING (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: plpgsql and INSERT/UPDATE/DELETE RETURNING
|
Список | 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 по дате отправления: