Received-SPF: pass (mail64-tx2: domain of uga.edu designates 157.56.240.245 as
	permitted sender) client-ip=157.56.240.245;
	envelope-from=nuse@uga.edu;
	helo=BL2PRD0210HT002.namprd02.prod.outlook.com ; .outlook.com ;
From: Bryan L Nuse <nuse@uga.edu>
To: Don Parris <parrisdc@gmail.com>
CC: "pgsql-sql@postgresql.org" <pgsql-sql@postgresql.org>
Subject: Re: Summing & Grouping in a Hierarchical Structure
Thread-Topic: [SQL] Summing & Grouping in a Hierarchical Structure
Thread-Index: 
 AQHOCyAJwSsJ7FlVmkKBmoOj7F52WZiFn+UAgAD/jACAACvkAIAAIgMAgAC3dACAAAcGAA==
Date: Sat, 23 Feb 2013 16:15:45 +0000
Message-ID: <7BEBA741-E416-4000-BE2D-B9196683A2A4@uga.edu>
References: 
 <CAJ-7yo=cpz0TocY4Qvb5e4=s3FB+VtHT3VV3gbUAz8Uqi7p6pw@mail.gmail.com>
	<CAH3i69moWcM9-mxaK5oiiY3o96X0V82QOyjXVDb2Jb-KrDQjog@mail.gmail.com>
	<CAJ-7yokc9-KzAd3BRrVPwQywz-f7wkBd2N9Cno-eM9m5gjUAww@mail.gmail.com>
	<CAJ-7yo=6dSoydFCEJo_9LSdUuoA1s68SFSwxzbwGh0oAKk0whw@mail.gmail.com>
	<8A586FDE-CC0A-4F26-AD19-1F89C2D9349E@uga.edu>
	<CAJ-7yokLGhpPhYFDPnZ2akQbndBfZ0jEfA+O4LQHDHBcaG-kPg@mail.gmail.com>
In-Reply-To: 
 <CAJ-7yokLGhpPhYFDPnZ2akQbndBfZ0jEfA+O4LQHDHBcaG-kPg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <E1F5EDD41BB0074290ECE32125D2E6BC@namprd02.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

>  That said, now that I have finally gotten the chance to try ltree, I thi=
nk I like it a lot.=20

Hello Don,

Yes, after looking at ltree --which I had not done before-- I have to agree=
 with Misa that it looks like the right solution for your problem.  That is=
 not to say that "brute force" SQL couldn't provide a workable arrangement;=
 but ltree looks very flexible, especially as it allows you to assign cost =
values to non-terminal nodes.  If it were me, though, I'd still make use of=
 VIEWs to report results of the workhorse queries:  staring at a list of it=
ems like "Transportation.Bicycle.Gear.Chain_ring" sounds like headache.  Th=
at's a matter of taste, of course.

Bryan


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