From: Tom Lane <tgl@sss.pgh.pa.us>
To: blo.talkto@gmail.com
Cc: pgsql-bugs@lists.postgresql.org, Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Subject: Re: BUG #17061: Impossible to query the fields of the tuple created by SEARCH BREADTH FIRST BY .. SET ..
Date: Thu, 17 Jun 2021 10:50:14 -0400
Message-ID: <972632.1623941414@sss.pgh.pa.us> (raw)
In-Reply-To: <17061-dd7f4825b7da3a9d@postgresql.org>
References: <17061-dd7f4825b7da3a9d@postgresql.org>
[ 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, blo.talkto@gmail.com, peter.eisentraut@enterprisedb.com
Subject: Re: BUG #17061: Impossible to query the fields of the tuple created by SEARCH BREADTH FIRST BY .. SET ..
In-Reply-To: <972632.1623941414@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox