Re: [HACKERS] Here it is - view permissions
От | The Hermit Hacker |
---|---|
Тема | Re: [HACKERS] Here it is - view permissions |
Дата | |
Msg-id | Pine.NEB.3.95.980223080529.17896B-100000@hub.org обсуждение исходный текст |
Ответ на | Re: [HACKERS] Here it is - view permissions (Mattias Kregert <matti@algonet.se>) |
Ответы |
Re: [HACKERS] Here it is - view permissions]
Re: [HACKERS] Here it is - view permissions |
Список | pgsql-hackers |
On Mon, 23 Feb 1998, Mattias Kregert wrote: > Bruce Momjian wrote: > > > > 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? > > Why does views default to 'select' permission for 'public'? > I think most people will never think of the possibility that others > will be able to SELECT their data through views. > Should not 'create view' at least print a NOTICE about this? Considering how much security we are putting around everything else, is it unreasonably to have both 'create view'/'create table' default to 'revoke all' to public, and 'grant all' to owner?
В списке pgsql-hackers по дате отправления: