| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2006-11-30 20:44:41 | Re: Any issues w/PostgreSQL 8.0.4 on Win2K3 x64? |
| Previous Message | Bill Bartlett | 2006-11-30 20:23:29 | Any issues w/PostgreSQL 8.0.4 on Win2K3 x64? |