| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: wCTE: about the name of the feature |
| Date: | 2011-02-24 19:35:30 |
| Message-ID: | A1D51E5C-8637-4056-B146-06214B054189@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Feb 24, 2011, at 10:43 AM, Robert Haas wrote:
>> 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?
>
> Great idea. I had the same complaint when I looked at this patch a
> year ago, but didn't come up with nearly as good an idea as to what to
> do about it.
I like "statement" better than "command," too, but love the acronym DMC. As in, "you want to Run [a] DMC." ;-P
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Radosław Smogura | 2011-02-24 20:02:06 | Re: Binary in/out for aclitem |
| Previous Message | Robert Haas | 2011-02-24 18:43:13 | Re: wCTE: about the name of the feature |