Re: wCTE: why not finish sub-updates at the end, not the beginning? - Mailing list pgsql-hackers

From David Fetter
Subject Re: wCTE: why not finish sub-updates at the end, not the beginning?
Date
Msg-id 20110226031635.GE27388@fetter.org
Whole thread Raw
In response to Re: wCTE: why not finish sub-updates at the end, not the beginning?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: wCTE: why not finish sub-updates at the end, not the beginning?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Feb 25, 2011 at 10:12:02PM -0500, Tom Lane wrote:
> David Fetter <david@fetter.org> writes:
> > What's the effect, if any, on CTEs that depend on each other
> > explicitly?
> 
> An error.  That would require mutual recursion, which we don't
> support for the SELECT case let alone data-modifying statements.

Sorry that was unclear.  Let's imagine there's a DELETE ... RETURNING
in one WITH, and an UPDATE in another that depends on that one.  Is
that still allowed?

Cheers,
David.
-- 
David Fetter <david@fetter.org> http://fetter.org/
Phone: +1 415 235 3778  AIM: dfetter666  Yahoo!: dfetter
Skype: davidfetter      XMPP: david.fetter@gmail.com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: wCTE: why not finish sub-updates at the end, not the beginning?
Next
From: Tom Lane
Date:
Subject: Re: wCTE: why not finish sub-updates at the end, not the beginning?