On Fri, 2007-21-12 at 18:05 -0400, Andrew Sullivan <ajs@crankycanuck.ca>
wrote:
> > > 2. Protect the content of a field from _some_ users on a given
> system,
> >
> > I would argue that (2) is reasonably well served today by setting up
> > separate databases for separate users.
>
> I thought actually this was one of the use-cases we were hearing.
> Different people using the same database (because the same data), with
> rules about the different staff being able to see this or that
> function body. I can easily imagine such a case, for instance, in a
> large organization with different departments and different
> responsibilities. It seems a shame that the only answer we have there
> is, "Give them different databases."
There is also Veil:
http://veil.projects.postgresql.org/curdocs/index.html
__
Marc
