Skip site navigation (1) Skip section navigation (2)

Re: Separation of clients' data within a database

From: "Leonel Nunez" <lnunez(at)enelserver(dot)com>
To: "John McCawley" <nospam(at)hardgeus(dot)com>
Cc: "Leonel Nunez" <lnunez(at)enelserver(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Separation of clients' data within a database
Date: 2006-11-30 20:32:09
Message-ID: 59483.189.155.96.115.1164918729.squirrel@enelserver.com (view raw or flat)
Thread:
Lists: pgsql-general
> It seems that this approach would suffer the same problem as the one I
> outlined in "1) Actually separate client data by table".  I would have
> to modify the logic of my web app...My web app currently handles all of
> the data, regardless of company, so it would have to aggregate the data
> from the different schemas when pulling data, and be smart enough to
> write back to the proper schemas when writing data.
>

on the public schema you can  have a table with the company and schema
and then select the default search path to the company's schema
and the rest of your app will be untouched

leonel



In response to

pgsql-general by date

Next:From: Joshua D. DrakeDate: 2006-11-30 20:44:41
Subject: Re: Any issues w/PostgreSQL 8.0.4 on Win2K3 x64?
Previous:From: Bill BartlettDate: 2006-11-30 20:23:29
Subject: Any issues w/PostgreSQL 8.0.4 on Win2K3 x64?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group