From: | Eugen Konkov <kes-kes(at)yandex(dot)ru> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: DOC not so clear |
Date: | 2019-01-15 06:37:37 |
Message-ID: | 1382435334.20190115083737@yandex.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Hello Tom,
Monday, January 14, 2019, 6:15:31 PM, you wrote:
> =?utf-8?q?PG_Doc_comments_form?= <noreply(at)postgresql(dot)org> writes:
>> https://www.postgresql.org/docs/current/queries-table-expressions.html#QUERIES-LATERAL
>>> The resulting row(s) are joined as usual with the rows they were computed
>>> from.
>> Here is not so clear what 'joined as usual' mean.
> Why not?
Advanced users may understand that, but from my beginner point of view
this is not. I do not understand that sentence until read whole text
and about LEFT JOIN LATERAL. Even now 'usual' may mean:
CROSS/RIGHT/FULL??
>> Probably DOC should explicitly say that if LATERAL function return empty set
>> then current row is excluded from result set
> That would be wrong for "LEFT JOIN LATERAL ...", so it does not seem
> like an improvement.
LATERAL != LEFT JOIN LATERAL
it would be more clear if DOC will be more explicit.
> regards, tom lane
--
Best regards,
Eugen Konkov
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2019-01-15 07:14:10 | Re: DOC not so clear |
Previous Message | Michael Paquier | 2019-01-14 23:50:00 | Re: Some typos in documentation |