From: Vik Fearing <vik@postgresfriends.org>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: SEARCH and CYCLE clauses
Date: Wed, 20 May 2020 15:04:20 +0200
Message-ID: <54e533c5-09e5-7f41-9892-d4e0f7c62598@postgresfriends.org> (raw)
In-Reply-To: <db80ceee-6f97-9b4a-8ee8-3ba0c58e5be2@2ndquadrant.com>
References: <db80ceee-6f97-9b4a-8ee8-3ba0c58e5be2@2ndquadrant.com>
On 5/20/20 1:46 PM, Peter Eisentraut wrote:
> I have implemented the SEARCH and CYCLE clauses.
YES!
> This is standard SQL syntax attached to a recursive CTE to compute a
> depth- or breadth-first ordering and cycle detection, respectively. This
> is just convenience syntax for what you can already do manually. The
> original discussion about recursive CTEs briefly mentioned these as
> something to do later but then it was never mentioned again.
>
> SQL specifies these in terms of syntactic transformations, and so that's
> how I have implemented them also, mainly in the rewriter.
I've attempted to do this several times but didn't get anywhere with it.
I'm looking forward to reviewing this.
(And maybe it will put me on the right path for implementing <unique
predicate>.)
--
Vik Fearing
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-hackers@postgresql.org
Cc: vik@postgresfriends.org, peter.eisentraut@2ndquadrant.com
Subject: Re: SEARCH and CYCLE clauses
In-Reply-To: <54e533c5-09e5-7f41-9892-d4e0f7c62598@postgresfriends.org>
* 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