From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: documentation for WITH RECURSIVE |
Date: | 2019-11-18 17:32:08 |
Message-ID: | 20712.1574098328@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> writes:
> One of our customers had problems with the syntax of WITH RECURSIVE. He
> suggested that the documentation should be improved, maybe with this
> sentence:
> "If any of the CTEs is recursive, the recursive keywork must be present
> after with", so to make sure that it does not refer to just one of the
> named subqueries.
Hm, was this intended for the SELECT man page (presumably in the
"WITH Clause" section), or for section 7.8?
In the SELECT page, I'd be inclined to put it after the para about
"queries need not be ordered" and phrase it more like
If there are multiple queries in the WITH clause, RECURSIVE can
be written only once, immediately after WITH. It applies to all
queries in the WITH clause (but has no effect on queries that do
not use either of these features).
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Kretschmer | 2019-11-18 19:12:09 | Re: documentation for WITH RECURSIVE |
Previous Message | Laurenz Albe | 2019-11-18 14:40:51 | Re: Role membership and DROP |