bricklen <brick...@gmail.com> wrote: > Kevin Grittner <kevin.gritt...@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). Possibly. The general tone of references to it, as well as the fact that it's still classified as being in beta testing, with a release number less than one, have put me off from looking at it closely. Is anyone using it in a situation where they have three thousand directly connected users? Or on a database backing a web site with five million hits a day? On a schema with over 300 tables (normalized, no partitioning)? If so, I'd be interested in hearing about it. -Kevin
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
