From: | Evgen Potemkin <evgent(at)ns(dot)terminal(dot)ru> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: Proposal of hierarchical queries, a la Oracle |
Date: | 2002-11-19 12:26:04 |
Message-ID: | Pine.LNX.4.33.0211191613050.7456-100000@ns.terminal.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
-Josh,
i don't be so thrilled:), with current implementation of /contrib/tablefunc
mine problem sill remains: i need to sort tree leaves in some order,
independent of tree itself. this can be fixed (in tablefunc) by addition to
connectby() one more field like 'order_by' or so. but it will be more difficult
to scale. for ex. if i need to make subquery with connect by, with tablefunc
i need to create view to do so. what if i need several different such
queries? of course this can be done with tablefunc, but IMHO mine
approach is a bit more 'native':)
---
.evgen
On Sat, 16 Nov 2002, Josh Berkus wrote:
> Evgren,
>
> > I want to propose the patch for adding the hierarchical queries
> > posibility.
> > It allows to construct queries a la Oracle for ex:
> > SELECT a,b FROM t CONNECT BY a PRIOR b START WITH cond;
>
> You'll be thrilled to know that this has already been implemented in
> PostgreSQL 7.3, as a /contrib module, by Joe Conway.
>
> Download 7.3b5 now if you can't wait; Joe would like more people to
> test his module, anyway.
>
> -Josh Berkus
>
From | Date | Subject | |
---|---|---|---|
Next Message | Evgen Potemkin | 2002-11-19 12:45:19 | Re: Proposal of hierarchical queries, a la Oracle |
Previous Message | Richard Huxton | 2002-11-19 12:25:31 | Re: index usage for query |