From: | jwieck(at)debis(dot)com (Jan Wieck) |
---|---|
To: | matti(at)algonet(dot)se (Mattias Kregert) |
Cc: | maillist(at)candle(dot)pha(dot)pa(dot)us, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Here it is - view permissions |
Date: | 1998-02-23 12:14:39 |
Message-ID: | m0y6wmN-000BFRC@orion.SAPserv.Hamburg.dsh.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
> 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?
Because the current ACL_WORLD_DEFAULT in include/utils/acl.h
is ACL_RD.
Anything not revoked explicitly is granted select to public.
Not only views. Think of it as a umask of 022.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#======================================== jwieck(at)debis(dot)com (Jan Wieck) #
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 1998-02-23 12:24:25 | Re: pl/{perl,pgsql} (was Re: AW: [HACKERS] triggers, views and ru |
Previous Message | Jan Wieck | 1998-02-23 12:06:21 | Re: [HACKERS] Backend crashes - what's going on here??? |