Re: [GENERAL] per-row security

2006-11-07 Thread Andrew Sullivan
On Mon, Nov 06, 2006 at 01:40:18PM -0800, Marc Munro wrote: You will of course be replicating the underlying tables and not the views, so your replication user will have to have full access to the unsecured data. This is natural and should not be a concern but may be worth explicitly

Re: [GENERAL] per-row security

2006-11-07 Thread Christopher Browne
[EMAIL PROTECTED] (Andrew Sullivan) wrote: On Mon, Nov 06, 2006 at 01:40:18PM -0800, Marc Munro wrote: You will of course be replicating the underlying tables and not the views, so your replication user will have to have full access to the unsecured data. This is natural and should not be a

Re: [GENERAL] Per-row security

2006-11-07 Thread Gurjeet Singh
On 11/4/06, Alexander Staubo [EMAIL PROTECTED] wrote: I am designing an application which requires fine-grained role-basedsecurity, where every logical object in the system has an ACL whichexpresses the permissions allowed by roles. Have you considered viel for Postgres ()? Here's what it says in

Re: [GENERAL] per-row security

2006-11-06 Thread Marc Munro
On Mon, 2006-06-11 at 22:27 +0100, Alexander Staubo wrote: On Nov 6, 2006, at 21:00 , Marc Munro wrote: For an alternative approach, you might want to check out Veil: http://pgfoundry.org/projects/veil Addendum: I took Veil to be undocumented since the source archive only comes with

[GENERAL] Per-row security

2006-11-03 Thread Alexander Staubo
I am designing an application which requires fine-grained role-based security, where every logical object in the system has an ACL which expresses the permissions allowed by roles. Implementing this on a high level is trivial, but it must scale, and scale extremely well. I have some fairly