Added to TODO:
* Allow INSERT ... DELETE ... RETURNING, namely allow the DELETE ... RETURNING to supply values to the INSERT
http://archives.postgresql.org/pgsql-hackers/2008-02/thrd2.php#00979
---------------------------------------------------------------------------
Jonah H. Harris wrote:
> On Sun, Feb 24, 2008 at 5:44 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > "Jonah H. Harris" <jonah.harris@gmail.com> writes:
> > > Not stupid, it doesn't work :) This was a limitation of the original
> > > design based on (IIRC) executor-related issues.
> >
> > There are definitional issues not only implementation ones; in
> > particular, in subquery-like cases it's entirely unclear how many times
> > the DML operation will or should get evaluated.
>
> Yup,that's what it was. I think I remember the trigger-level and
> top-level executor-related stuff. If I'm in that area of the code
> soon, I'll see how much would be involved and if I think I have enough
> time, submit a proposal for it.
>
> --
> Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
> EnterpriseDB Corporation | fax: 732.331.1301
> 499 Thornall Street, 2nd Floor | jonah.harris@enterprisedb.com
> Edison, NJ 08837 | http://www.enterprisedb.com/
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
-- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB
http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
