| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "John McCawley" <nospam(at)hardgeus(dot)com>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Separation of clients' data within a database |
| Date: | 2006-11-30 18:57:38 |
| Message-ID: | 456ED542.EE98.0025.0@wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>>> On Thu, Nov 30, 2006 at 12:48 PM, in message
<456F2795(dot)3070603(at)hardgeus(dot)com>,
John McCawley <nospam(at)hardgeus(dot)com> wrote:
>
> 4) Create views for each client that filter the underlying table data
to
> only show them their data. The only database objects they would have
> read permission on are these views. Come to think of it, this is
> probably the best way to go.
That's what I'd be looking at. Be sure to revoke public rights on the
database and public schema, and grant back the rights you want. Think
about using the schemas to segregate the views for the various clients.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John McCawley | 2006-11-30 19:28:43 | Re: Separation of clients' data within a database |
| Previous Message | John McCawley | 2006-11-30 18:48:53 | Separation of clients' data within a database |