Re: "writable CTEs"

From: David Fetter <david(at)fetter(dot)org>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: "writable CTEs"
Date: 2010-12-27 22:06:12
Message-ID: 20101227220612.GB25421@fetter.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Dec 27, 2010 at 11:47:14PM +0200, Peter Eisentraut wrote:
> On ons, 2010-12-22 at 20:44 +0200, Marko Tiikkaja wrote:
> > On 2010-12-22 8:28 PM, Peter Eisentraut wrote:
> > > As a side note, I think the term "writable CTE" is a misnomer. The CTE
> > > is not writable. The CTE is the result of a write operation.
> > >
> > > A writable CTE would look like this:
> > >
> > > WITH foo AS (SELECT ...) UPDATE foo SET ...
> > >
> > > a bit like an updatable view.
> > >
> > > AFAICT, the current patch doesn't use the term, so there is no problem,
> > > but just for those who are preparing propaganda and such.
> >
> > I think I've used "DML WITH" in the patch, but I don't like that either.
> > Naming this feature seems to be quite a challenge.
>
> *Writing* CTEs is more accurate.

OK :)

On the bright side, we have a decades-long tradition of horrible names
on this project, one early example of which is a name that abbreviates
the phrase, 'POST-"interactive GRaphics REtrieval System."' ;)

Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2010-12-27 22:36:42 Re: SSI memory mitigation & false positive degradation
Previous Message Robert Haas 2010-12-27 22:04:15 Re: Bug in configure script for build postgresql