From: Achilleus Mantzios <achill@matrix.gatewaynet.com>
To: Gregory Brauer <greg@wildbrain.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Trees in SQL
Date: Mon, 27 May 2002 15:00:16 +0300 (EEST)
Message-ID: <Pine.LNX.4.33.0205271438080.1584-100000@matrix.gatewaynet.com> (raw)
In-Reply-To: <3CEE818B.9020702@wildbrain.com>
On Fri, 24 May 2002, Gregory Brauer wrote:
I have exactly the same situation.
Some work (argued to have better performance than Celko's implementation)
has been done by Miguel Sofer. (see http://www.utdt.edu/~mig/trees.tar.gz)
One fast solution would be using pgsql arrays and the contrib/array
package.
However Oleg's and Theodor's contrib/tree solution looks the most
attractive.
I will ask my wife today to do a translation of the doc,
(hoping russian and yugoslavian are alike :)
>
> I hope this isn't an overly broad topic that ends up diverging into graph
> theory, but I have a tree structure of identical items (analogous to a
> filesystem directory tree) that I need to store in Postgres. The
> "obvious" design is to give the table that will represent these objects
> a field identifying its "parent" that is a relation to the same table.
> However, this seems to make many common SQL queries rather difficult.
>
> What sort of strategies are best for storing tree structures in a
> relational database, and how would one structure SQL queries to find,
> say, "all of the children anywhere under this node", or to represent
> the condition "if this node is a child at any depth under this other
> node"? Are there good strategies for preventing cycles?
>
> I'd appreciate any insights anyone can give.
>
> Thanks.
>
> Greg Brauer
> greg@wildbrain.com
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>
--
Achilleus Mantzios
S/W Engineer
IT dept
Dynacom Tankers Mngmt
tel: +30-10-8981112
fax: +30-10-8981877
email: achill@matrix.gatewaynet.com
mantzios@softlab.ece.ntua.gr
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: achill@matrix.gatewaynet.com, greg@wildbrain.com
Subject: Re: Trees in SQL
In-Reply-To: <Pine.LNX.4.33.0205271438080.1584-100000@matrix.gatewaynet.com>
References: <3CEE818B.9020702@wildbrain.com> <Pine.LNX.4.33.0205271438080.1584-100000@matrix.gatewaynet.com>
* 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