From: Josh Berkus <josh@agliodbs.com>
To: pgsql-hackers@postgresql.org
Cc: chris@pgsql.com
Subject: Re: Schema boggle...
Date: Wed, 5 Nov 2003 13:58:34 -0800
Message-ID: <200311051358.34826.josh@agliodbs.com> (raw)
In-Reply-To: <E1AHVFF-0002Up-75@noon.pghoster.com>
References: <E1AHVFF-0002Up-75@noon.pghoster.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
partition client data. Far better to have monolithic tables with a
"client_id" column and then construct *views* which are available in each
schema only to that client. Otherwise, as you've discovered, top-level
management becomes a royal pain.
I'd be happy to discuss this further on PGSQL-SQL, which is really the
appropriate mailing list.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: josh@agliodbs.com, pgsql-hackers@postgresql.org, chris@pgsql.com
Subject: Re: Schema boggle...
In-Reply-To: <200311051358.34826.josh@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox