Re: Writeable CTEs Desgin Doc on Wiki - Mailing list pgsql-hackers

From Marko Tiikkaja
Subject Re: Writeable CTEs Desgin Doc on Wiki
Date
Msg-id 4C6A3D81.9090406@cs.helsinki.fi
Whole thread Raw
In response to Re: Writeable CTEs Desgin Doc on Wiki  (Hitoshi Harada <umi.tanuki@gmail.com>)
List pgsql-hackers
On 2010-08-17 6:41 AM +0300, Hitoshi Harada wrote:
> 2010/8/17 Robert Haas<robertmhaas@gmail.com>:
>> There are really two separate features here, and it might be worth
>> giving them separate names and separate designs (and separate
>> patches).  Allowing the main query to be an insert, update, or delete
>> seems easier than allowing the toplevel CTEs to contain those
>> constructs, although I might be wrong about that.
>>
>> Under features, what is DCL?  There has been previous talk of allowing
>> WITH (COPY ...) and I am personally of the opinion that it would be
>> nice to be able to do WITH (EXPLAIN ...).  DDL seems like a poor idea.
>
> So, there are three? One for allowing the main query to be an insert,
> update, or delete, one for the main subject of writeable CTE with
> insert, update, delete and one for allowing COPY to return rows. I am
> attracted by such COPY functionality.
>
> And the first part seems easier to be committed separately. Is it
> possible to get it in by only adding syntax and little parser/planner
> modification, or more executor code?

It's not that simple, see:
http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php


Regards,
Marko Tiikkaja


pgsql-hackers by date:

Previous
From: Jaime Casanova
Date:
Subject: Re: Per-column collation, proof of concept
Next
From: Magnus Hagander
Date:
Subject: Re: Git migration timeline