On Thu, Feb 24, 2011 at 11:20:48AM -0500, Tom Lane wrote: > 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?
+1 If we ever decide add in what I'd originally envisioned, namely DCL and DDL, the name continues to describe what's going on :) Cheers, David. -- David Fetter <da...@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fet...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
