Dealing with heirarchal data is precisely what ltree was designed to do (using GiST indexes).

I do tend to agree that this is not ideally done in a relational database, which is the purpose of this post. I'm trying to find a different/better solution but so far am coming up empty. :(

- dEvNuL