Re: self referencing tables/ nested sets etc...

From: "Shawn Harrison" <harrison(at)tbc(dot)net>
To: "Joe Conway" <mail(at)joeconway(dot)com>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: self referencing tables/ nested sets etc...
Date: 2004-03-25 15:20:07
Message-ID: 000101c41348$e72919a0$119de3cf@THP63412
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)joeconway(dot)com>
To: "Shawn Harrison" <harrison(at)tbc(dot)net>
Cc: <pgsql-general(at)postgresql(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message sferriol 2004-03-25 15:29:48 bug in delete rule ?
Previous Message Jeff Eckermann 2004-03-25 14:55:41 Re: Adding flexibilty to queries