From: Frank Joerdens <frank@joerdens.de>
To: Tulassay Zsolt <zsolt@tek.bke.hu>
Cc: pgsql-sql@postgresql.org
Subject: Re: Tree structure table normalization problem (do I need atrigger?)
Date: Tue, 19 Dec 2000 14:17:58 +0100
Message-ID: <3A3F6006.ECDE92AE@joerdens.de> (raw)
References: <Pine.LNX.4.10.10012191001080.20512-100000@tek.tek.bke.hu>
Tulassay Zsolt wrote:
[ . . . ]
> The SQL stuff of that nested set structure is fairly easy, I wrote some
> quick'n'dirty plpgsql functions that will do inserts, updates, deletes
> from the tree, display level number etc.
What scared me about it in particular was one scenario where you try to delete a subtree.
This would normally leave a gap, since the structure is based on the worm's ability to get
from one node to the next with an increment of just 1. Once you had a subtree deleted,
you'd either would have to have the worm leap-frog (a leaping frog-worm?!! :)) the gap or
update an entire half of the tree to close it . . . then my brain started to hurt and I
gave up.
> I can send it to you if you like (please allow a few days since I
> have several exams at the university this week).
Sure, I'd like to have a look at it!
Thanks, Frank
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: frank@joerdens.de, zsolt@tek.bke.hu
Subject: Re: Tree structure table normalization problem (do I need atrigger?)
In-Reply-To: <3A3F6006.ECDE92AE@joerdens.de>
References: <Pine.LNX.4.10.10012191001080.20512-100000@tek.tek.bke.hu> <3A3F6006.ECDE92AE@joerdens.de>
* 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