Content-Type: text/plain;
  charset="iso-8859-1"
From: Josh Berkus <josh@agliodbs.com>
Reply-To: josh@agliodbs.com
Organization: Aglio Database Solutions
To: pgsql-hackers@postgresql.org
Subject: Re: Schema boggle...
Date: Wed, 5 Nov 2003 13:58:34 -0800
User-Agent: KMail/1.4.3
References: <E1AHVFF-0002Up-75@noon.pghoster.com>
In-Reply-To: <E1AHVFF-0002Up-75@noon.pghoster.com>
Cc: chris@pgsql.com
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200311051358.34826.josh@agliodbs.com>

Chris,

>  I work with Marc Fournier, for those who don't know, and have been
> working extensively with the schemas feature for Hub.Org's new Account
> Management package. Each client's data is stored in a seperate schema
> set asside just for them (though they will never have direct access to
> it, it helps us "balance" out the data. Each schema has the same set of
> tables, with which different data is stored, depending on the client.

While this is an interesting use of Schema, it is not, IMHO, a good way to=
=20
partition client data.    Far better to have monolithic tables with a=20
"client_id" column and then construct *views* which are available in each=
=20
schema only to that client.   Otherwise, as you've discovered, top-level=20
management becomes a royal pain.

I'd be happy to discuss this further on PGSQL-SQL, which is really the=20
appropriate mailing list.

--=20
-Josh Berkus
 Aglio Database Solutions
 San Francisco