| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
| Cc: | pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: INS/UPD/DEL RETURNING for 8.2 |
| Date: | 2006-03-02 23:45:38 |
| Message-ID: | 1141343138.24513.13.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
On Thu, 2006-03-02 at 17:51 -0500, Jonah H. Harris wrote:
> Patch for core and PL/pgSQL to support the INSERT/UPDATE/DELETE
> RETURNING syntax in 8.2
I wonder if we should try to consistently treat an INSERT/UPDATE/DELETE
with a RETURNING clause like a SELECT with an equivalent target list.
For example, should it be possible to write:
FOR x in DELETE FROM t1 WHERE ... RETURNING t1.x LOOP
...
END LOOP;
Or open a cursor for a data-modifying statement with a RETURNING clause,
etc.
-Neil
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-03-03 00:07:23 | Re: Fix overflow of bgwriter's request queue |
| Previous Message | Jonah H. Harris | 2006-03-02 22:51:20 | INS/UPD/DEL RETURNING for 8.2 |