Received: from localhost (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP id EC95347650E
	for <pgsql-sql@postgresql.org>; Fri, 22 Nov 2002 17:32:34 -0500 (EST)
Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250])
	by postgresql.org (Postfix) with ESMTP id 634934764BF
	for <pgsql-sql@postgresql.org>; Fri, 22 Nov 2002 17:32:34 -0500 (EST)
Received: from [216.135.165.74] (account <josh@agliodbs.com>)
	by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.5.9)
	with HTTP id 1837760; Fri, 22 Nov 2002 14:37:00 -0800
From: "Josh Berkus" <josh@agliodbs.com>
Subject: Re: Trees: maintaining pathnames
To: "Dan Langille" <dan@langille.org>, pgsql-sql@postgresql.org
X-Mailer: CommuniGate Pro Web Mailer v.3.5.9
Date: Fri, 22 Nov 2002 14:37:00 -0800
Message-ID: <web-1837760@davinci.ethosmedia.com>
In-Reply-To: <3DDE6691.19184.C4BEF7D4@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: by AMaViS new-20020517
X-Archive-Number: 200211/351
X-Sequence-Number: 10493

Dan,

Looks good to me.  It's the same thing I do for the Celko tree
structures in one application -- I have a cache table holding such
things as level and parent_id for each node, values which can only be
generated from the source tables through slow aggregates.

Also, the use of a child table to hold the pathnames should cure your
"cascading trigger" problem.

-Josh Berkus