To: pgsql-sql@postgresql.org
From: Thomas Kellerer <spam_eater@gmx.net>
Subject: Re: Using Ltree For Hierarchical Structures
Date: Tue, 26 Feb 2013 19:43:32 +0100
Lines: 21
Message-ID: <kgivo7$rg4$1@ger.gmane.org>
References: 
 <CAJ-7yonEdms9gwr8mzfXQUFQAoUScykPec=6n9K2s93JMWPj7A@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de;
	rv:1.8.1.21) Gecko/20090302 Thunderbird/2.0.0.21 Mnenhy/0.7.5.666
In-Reply-To: 
 <CAJ-7yonEdms9gwr8mzfXQUFQAoUScykPec=6n9K2s93JMWPj7A@mail.gmail.com>
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

Don Parris wrote on 24.02.2013 23:20:
> With many thanks to Misa and others who helped out with my question
> about working with hierarchical data, I have now written a blog post
> on how I implemented the ltree module to solve my problem.
>
> http://dcparris.net/2013/02/24/using-ltree-hierarchical-postgresql/
>
> Frankly, if you work with hierarchical data, I'm not sure I could
> recommend it strongly enough.  I should think that even experienced,
> advanced SQL gurus would appreciate the simplicity ltree offers, when
> compared to the ugly table designs and recursive queries in order to
> work with hierarchical structures.
>
> I really hope this blog post will help others in the same boat.
>

How do you ensure referential integrity with this approach?
(i.e. make sure that all elements from the path column actually point to an existing category)

Thomas


-- 
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql