Re: BUG #17061: Impossible to query the fields of the tuple created by SEARCH BREADTH FIRST BY .. SET ..

Поиск
Список
Период
Сортировка
Искать
От
Tom Lane
Тема
Re: BUG #17061: Impossible to query the fields of the tuple created by SEARCH BREADTH FIRST BY .. SET ..
Дата
Msg-id
1550447.1632061226@sss.pgh.pa.us
Ответ на
Список
Дерево обсуждения
BUG #17061: Impossible to query the fields of the tuple created by SEARCH BREADTH FIRST BY .. SET .. PG Bug reporting form <noreply@postgresql.org>
Re: BUG #17061: Impossible to query the fields of the tuple created by SEARCH BREADTH FIRST BY .. SET .. Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: BUG #17061: Impossible to query the fields of the tuple created by SEARCH BREADTH FIRST BY .. SET .. Michael Paquier <michael@paquier.xyz>
Re: BUG #17061: Impossible to query the fields of the tuple created by SEARCH BREADTH FIRST BY .. SET .. talk to ben <blo.talkto@gmail.com>
Re: BUG #17061: Impossible to query the fields of the tuple created by SEARCH BREADTH FIRST BY .. SET .. Jaime Casanova <jcasanov@systemguards.com.ec>
Re: BUG #17061: Impossible to query the fields of the tuple created by SEARCH BREADTH FIRST BY .. SET .. Tom Lane <tgl@sss.pgh.pa.us>
Jaime Casanova  writes:
> Just to add fuel to the fire, I just noted that you cannot create a view
> based on a recursive CTE using this syntax.
> ...
> ERROR:  column "breadth" has pseudo-type record

Yeah, I've run into that too.  There's no time to reconsider the
implementation for v14, but I'd sure like to see this revisited
later.  I'm kind of wondering if, instead of a single RECORD
column, we could add each of the SEARCH columns and the depth
column as a separate resjunk column.  (However, I'm not sure
how to extend that approach to the DEPTH FIRST case, which
wants an array.)

			regards, tom lane


В списке pgsql-bugs по дате отправления
От: PG Bug reporting form
Дата:
От: Tom Lane
Дата:
FAQ