Skip site navigation (1) Skip section navigation (2)

wCTE: about the name of the feature

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: wCTE: about the name of the feature
Date: 2011-02-24 16:20:48
Message-ID: 12023.1298564448@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
The wCTE patch refers to the feature it's adding as "DML WITH".  I'm
still pretty unhappy with that terminology.  In my view of the world,
"DML" includes SELECT as well as INSERT/UPDATE/DELETE.  The wikipedia
entry about the term
http://en.wikipedia.org/wiki/Data_Manipulation_Language
agrees that that's at least the majority usage, and even our own docs
seem to use it to include SELECT as often as not.  Since the distinction
is absolutely critical to talking about this feature sensibly, I don't
think it's a good plan to use an acronym that is guaranteed to produce
uncertainty in the reader's mind.

The best idea I have at the moment is to spell out "data modifying
command" (or "statement") rather than relying on the acronym.
In the code, we could change hasDmlWith to hasModifyingWith, for
example.  The error messages could read like
	data-modifying statement in WITH is not allowed in a view

Comments?

			regards, tom lane

Responses

pgsql-hackers by date

Next:From: Marko TiikkajaDate: 2011-02-24 16:33:08
Subject: Re: wCTE: about the name of the feature
Previous:From: Tom LaneDate: 2011-02-24 16:02:57
Subject: Re: Review: Fix snapshot taking inconsistencies

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group