From: | Rodrigo Gonzalez <rjgonzale(at)gmail(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 19:35:24 |
Message-ID: | 456F327C.30804@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
search_path="$user" in postgresql.conf
and you create one schema for each user with the user name as name....
Rodrigo
John McCawley wrote:
> 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.
>
> Leonel Nunez wrote:
>
>> why don't you create a schema for every company and grant
>> permissions to
>> use the shchema to only the user that needs to use that??
>>
>> more info :
>> http://www.postgresql.org/docs/8.1/static/ddl-schemas.html
>>
>>
>> Leonel
>>
>>
>>
>>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2006-11-30 19:44:54 | Re: Separation of clients' data within a database |
Previous Message | John McCawley | 2006-11-30 19:28:43 | Re: Separation of clients' data within a database |