Re: self referencing tables/ nested sets etc... - Mailing list pgsql-general

From Shawn Harrison
Subject Re: self referencing tables/ nested sets etc...
Date
Msg-id 000101c41348$e72919a0$119de3cf@THP63412
Whole thread Raw
In response to self referencing tables/ nested sets etc...  (Rob Hoopman <rob@tuna.nl>)
List pgsql-general
Joe,

That's cool! Thanks for the tip. It looks like your "branch" is my
"ancestry". I'll look in contrib more often. I could use connectby() instead
of my homebrew plpgsql functions.

Shawn

----- Original Message -----
From: "Joe Conway" <mail@joeconway.com>
To: "Shawn Harrison" <harrison@tbc.net>
Cc: <pgsql-general@postgresql.org>
Sent: Wednesday, March 24, 2004 11:37 PM
Subject: Re: [GENERAL] self referencing tables/ nested sets etc...


> Shawn Harrison wrote:
> > Forbes. But my own approach is to let the unique id of each object serve
as
> > its "key" in the nested set key-chain (which I call its "ancestry"), and
> > separate the ids with path separator, e.g.:
>
> See connectby() in contrib/tablefunc. It produces much the same output
> dynamically.
>
> Joe


pgsql-general by date:

Previous
From: Guy Fraser
Date:
Subject: Re: PHP or JSP? That is the question.
Next
From: "Nilton Yudiro Ikezire"
Date:
Subject: Compiling