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

From Tom Lane
Subject Re: BUG #17061: Impossible to query the fields of the tuple created by SEARCH BREADTH FIRST BY .. SET ..
Date
Msg-id 972632.1623941414@sss.pgh.pa.us
Whole thread Raw
In response to BUG #17061: Impossible to query the fields of the tuple created by SEARCH BREADTH FIRST BY .. SET ..  (PG Bug reporting form <noreply@postgresql.org>)
Responses 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>)
List pgsql-bugs
[ screwed up the cc somehow the first time, sorry for the duplicate ]

PG Bug reporting form <noreply@postgresql.org> writes:
> WITH RECURSIVE mtree(id, name) AS ( ...
> ) SEARCH BREADTH FIRST BY id SET breadth
> SELECT (breadth)."*DEPTH*"
> FROM mtree m;
> ERROR:  CTE m does not have attribute 3

Yeah, I get that with "SELECT (breadth).*" as well.  I'm not entirely sure
what this silly-looking syntax is supposed to mean, but it seems to be
adding an output column named "breadth" to the CTE.  The error is
occurring because said column has not been added to the relevant
CommonTableExpr struct.  Peter?

            regards, tom lane



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows
Next
From: Tom Lane
Date:
Subject: Re: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows