Re: [GENERAL] postgresql how to duplicate rows in result.

Поиск
Список
Период
Сортировка
От Merlin Moncure
Тема Re: [GENERAL] postgresql how to duplicate rows in result.
Дата
Msg-id CAHyXU0wU=g+fCSF9D8NpboeH=uaw7yOo=TzL2jCsQwCiGyQuDA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [GENERAL] postgresql how to duplicate rows in result.  ("David G. Johnston" <david.g.johnston@gmail.com>)
Ответы Re: [GENERAL] postgresql how to duplicate rows in result.  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-general
On Thu, Feb 16, 2017 at 10:27 AM, David G. Johnston
<david.g.johnston@gmail.com> wrote:
> If it wasn't lateral the reference to number in "generate_series(1, number)"
> would fail.

huh -- I didn't know that!  Testing it out, all JOIN types imply
LATERAL if the function call is tlist SRF style (which is pretty werid
IMO)  I tend to avoid optional words (with the important exception of
AS for column list renames) but I think it's a good idea to disclose
LATERAL in this case.  It's a big clue to the reader what is going on
and the expanded form:

SELECT foo.* FROM foo CROSS JOIN LATERAL (SELECT a,b FROM func(foo.bar)) q;

... requires LATERAL to be explicitly stated.  This form is more
general since it can be cleanly used when func() returns more than one
column.

merlin


В списке pgsql-general по дате отправления:

Предыдущее
От: Alexey Lesovsky
Дата:
Сообщение: [GENERAL] save PGresult to file.
Следующее
От: Jeff Janes
Дата:
Сообщение: Re: [GENERAL] Bad planning data resulting in OOM killing of postgres