X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.2])
	by svr1.postgresql.org (Postfix) with ESMTP
	id 7FEAED1BB59; Thu,  6 Nov 2003 05:03:47 +0000 (GMT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024)
	with ESMTP id 88911-08; Thu,  6 Nov 2003 01:03:16 -0400 (AST)
Received: from davinci.ethosmedia.com (server228.ethosmedia.com
	[209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP
	id 26CACD1B923; Thu,  6 Nov 2003 01:03:15 -0400 (AST)
Received: from [63.195.55.98] (HELO spooky)
	by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2)
	with ESMTP id 3875574; Wed, 05 Nov 2003 21:03:56 -0800
Content-Type: text/plain;
  charset="iso-8859-1"
From: Josh Berkus <josh@agliodbs.com>
Organization: Aglio Database Solutions
To: Chris Bowlby <excalibur@hub.org>,
	"Marc G. Fournier" <scrappy@postgresql.org>
Subject: Re: [HACKERS] Schema boggle...
Date: Wed, 5 Nov 2003 21:01:58 -0800
User-Agent: KMail/1.4.3
Cc: pgsql-sql@postgresql.org
References: <200311051358.34826.josh@agliodbs.com>
	<5.2.1.1.0.20031105220602.00a19700@mail.pgsql.com>
In-Reply-To: <5.2.1.1.0.20031105220602.00a19700@mail.pgsql.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <200311052101.58892.josh@agliodbs.com>
X-Virus-Scanned: by amavisd-new at postgresql.org
X-Archive-Number: 200311/32
X-Sequence-Number: 15847

Chris,

>   Monolithic tables have their uses, I don't and wont contest that, however
> we've been using a monolithic structure in our current AMS distribution and
<snip>
> dataset. That and I'm more confident working on a 3D level, versus 2D, the
> schema levels introduce the third dimension into my structure and simplify
> visualizing how I want things to work.

TMI!  TMI!  Ok, I believe that it works for you.   You've made a tradeoff, 
though, and some operations that were simple in the old monolithic structure 
will now be more difficult -- however worthwhile the overall tradeoff may be.

> resulting query as he suggested, I just need to learn plpgsql programming
> so that I can work out all of the details (Tom, I might bug you about that
> once in a while).

Just go ahead and post your PL/pgSQL questions to the list.  There are people 
on this list who've written thousands of lines of PL/pgSQL ...

-- 
Josh Berkus
Aglio Database Solutions
San Francisco