Skip site navigation (1) Skip section navigation (2)

Re: Hierarchical queries a la Oracle. Patch.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Evgen Potemkin <evgent(at)ns(dot)terminal(dot)ru>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: Hierarchical queries a la Oracle. Patch.
Date: 2002-11-23 04:55:24
Message-ID: 3300.1038027324@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-patches
Evgen Potemkin <evgent(at)ns(dot)terminal(dot)ru> writes:
> This is a patch which allows PG to make hierarchical queries a la Oracle do.

This is an extremely large patch with an extreme paucity of
documentation.  For example, I searched in vain for any explanation of
what the varfake field does or why it's necessary to add such a field
to every single Var node.  That's a nontrivial amount of overhead to
pay for a feature that relatively few people will use.  (And if it is
needed, you've surely neglected to deal with it in an awful lot of
places that create or manipulate Vars.  Perhaps a new node type would
be a better idea than overloading Var like this.  Misusing Const is a
bad idea too.)

I'm also wondering what you may have broken in altering the handling of
HAVING clauses in planner.c.  What's going on there?

A more global concern is whether this really implements what Oracle
calls CONNECT BY.  I had the idea that that was a deeper feature than
just controlling the ordering of output, which AFAICT is what this does.
Also, the documents I've been able to find on the Web suggest that
Oracle's view of the syntax for the feature is only tenuously related
to what you've implemented here.

			regards, tom lane

In response to

Responses

pgsql-patches by date

Next:From: Evgen PotemkinDate: 2002-11-23 10:37:48
Subject: Re: Hierarchical queries a la Oracle. Patch.
Previous:From: Bruce MomjianDate: 2002-11-23 04:05:53
Subject: Re: Transaction safe Truncate

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group