Re: Schema boggle...

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Cc: chris(at)pgsql(dot)com
Subject: Re: Schema boggle...
Date: 2003-11-05 21:58:34
Message-ID: 200311051358.34826.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-sql

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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Marc G. Fournier 2003-11-05 22:02:58 Re: Schema boggle...
Previous Message Tom Lane 2003-11-05 21:50:48 Re: \xDD patch for 7.5devel

Browse pgsql-sql by date

  From Date Subject
Next Message Marc G. Fournier 2003-11-06 01:45:39 Re: Schema boggle...
Previous Message Jerome Alet 2003-11-05 21:40:41 avoid circular references