IMHO, Veil is very strange project. Instead of concentrating on good
support of updatable views, developers are trying to reinvent the
wheel. Actually, if restriction-and-projection views would be
updatable w/o overhead (such as creating rules), there'll no need in
such project. It's one of the maj
Dave,
Sorry to be so late in responding to this but I may have just the
solution for you.
Please check out Veil at pgfoundry. This is an add-on to Postgres that
I think does just what you are looking for. As the developer of this
project, I would be pleased to offer you assistance.
http://veil.
Hi all.
Implimenting a custom permission system is fairly easy to do with
triggers, views, and rules.
Here is my suggestion. Put your data tables in a shadow schema and
don't give users access to them. Then create views that select the
information from the tables that they have access to.
David Garamond <[EMAIL PROTECTED]> writes:
> Hi,
>
> Our current project requires a fine-grained permission system (row-level
> and possibly column-level as well). We have a pretty large (tens of
> thousands) of users in the 'party' table. I'm thinking of choosing
> Unix-style security for now (ad
Hi,
Our current project requires a fine-grained permission system (row-level
and possibly column-level as well). We have a pretty large (tens of
thousands) of users in the 'party' table. I'm thinking of choosing
Unix-style security for now (adding 'ugo' and 'owner' and 'group'
columns to each tabl
