Re: SQL2011 and writeable CTE - Mailing list pgsql-hackers

From Hitoshi Harada
Subject Re: SQL2011 and writeable CTE
Date
Msg-id AANLkTi=Ynm6VV003rs-Tw-t2H912_M11Ft+H6G6PTStu@mail.gmail.com
Whole thread Raw
In response to Re: SQL2011 and writeable CTE  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: SQL2011 and writeable CTE
Re: SQL2011 and writeable CTE
List pgsql-hackers
2010/11/8 Peter Eisentraut <peter_e@gmx.net>:
> On sön, 2010-11-07 at 21:28 +0900, Hitoshi Harada wrote:
>> I've read this Peter's post:
>>
>> http://petereisentraut.blogspot.com/2010/04/news-from-sql-standard.html
>>
>> which says in SQL2011 has a new feature:
>>
>> > Combined data change and retrieval. PostgreSQL does something like this with RETURNING, but this feature is more
elaborateand allows the writing of "delta tables". 
>>
>> And I heard from sources that this "delta table" contains something
>> like writeable CTEs. Couldn't you share something about it if
>> possible? I just don't like to design something that will be similar
>> to but different from the standard.
>
> Yeah, actually, after further study, this has nothing to do with actual
> delta tables, and it is in fact exactly the RETURNING feature in
> combination with the possibility to embed it into a superordinate query.

Hmm, this looks very different from our writeable CTEs. And I can see
many issues like syntax ambiguity and execution order if we support
it. AFAIK the most significant reason why we are working on CTEs is
that CTEs are regarded as something like materialized table.

So I think we are going on writeable "CTEs" unless there are no
objection rather than pursuing the standard.
Thanks for sharing anyway.



--
Hitoshi Harada


pgsql-hackers by date:

Previous
From: Hitoshi Harada
Date:
Subject: Re: How to share the result data of separated plan
Next
From: Tom Lane
Date:
Subject: Re: UNION ALL has higher cost than inheritance