> This flag is useful anyway. We change the world now that ALL
> views are overriding the acl checks. If we have this flag we
> can setup views that behave like before (user cannot see
> anything through the view he cannot see without) and use the
> overriding only in cases we need it (like for the pg_user
> permissions problem). I'll work on it.
OK, but why would anyone want the old behavior?
I guess if you have a table that is not select-able by everyone, and you
create a view on it, the default permits will allow select to others.
You would have to set the permit on that view. Is there more to that
pg_class flag you want to add?
In response to
pgsql-hackers by date
|Next:||From: Ryan Kirkpatrick||Date: 1998-02-21 00:54:46|
|Subject: Re: [HACKERS] Platform status|
|Previous:||From: Humberto Rondon Parra||Date: 1998-02-20 21:50:51|