Re: leaky views, yet again - Mailing list pgsql-hackers

From bricklen
Subject Re: leaky views, yet again
Date
Msg-id AANLkTik=vwx5EDU55fiP_XH6c=hiNM9jvA82mD4DzhcP@mail.gmail.com
Whole thread Raw
In response to Re: leaky views, yet again  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: leaky views, yet again
Re: leaky views, yet again
List pgsql-hackers
On Tue, Oct 5, 2010 at 1:25 PM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
> Right now this is managed by query classes in our Java applications,
> but as we're moving to a variety of new and different technologies
> it's getting harder for the DBAs to ensure that nothing is leaking
> to inappropriate recipients.  :-(  I think we're going to need to
> move more of the enforcement to database views and/or security
> restrictions based on database roles.

Does  Veil cover some of those needs?
http://veil.projects.postgresql.org/curdocs/index.html
I've never used it, but from what I recall hearing about it, it did
something similar (I thought).


pgsql-hackers by date:

Previous
From: Bernd Helmle
Date:
Subject: Re: WIP: Triggers on VIEWs
Next
From: Josh Berkus
Date:
Subject: Re: Issues with Quorum Commit