| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: "writable CTEs" |
| Date: | 2010-12-28 02:51:01 |
| Message-ID: | AANLkTimeDKgHNGvfg1KpAtZmL-x7q0mZ3-UzxCo7U1dO@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Dec 27, 2010 at 9:28 PM, David Fetter <david(at)fetter(dot)org> wrote:
> On Tue, Dec 28, 2010 at 12:19:47AM +0000, Peter Geoghegan wrote:
>> It's worth noting that officially (i.e. in the docs), we don't even
>> call CTEs CTEs at any point. We call them WITH queries. I think that
>> that's a mistake because we call them CTEs everywhere else.
>
> Agreed.
>
>> Is there interest in correcting this, by putting "CTEs" or "Common
>> table expressions" in parenthesis after "WITH queries" in the docs
>> at certain select places? I could write a documentation patch.
>
> +1 :)
Would it make sense to work a section into the documentation
explaining the semantics of CTEs? e.g., evaluate-once.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2010-12-28 03:05:49 | Re: "writable CTEs" |
| Previous Message | David Fetter | 2010-12-28 02:28:20 | Re: "writable CTEs" |