From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | matti(at)algonet(dot)se (Mattias Kregert) |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Here it is - view permissions |
Date: | 1998-02-23 13:10:59 |
Message-ID: | 199802231310.IAA20810@candle.pha.pa.us |
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?
All tables are created with default permissions for SELECT to PUBLIC, so
views are no different.
--
Bruce Momjian
maillist(at)candle(dot)pha(dot)pa(dot)us
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1998-02-23 13:15:17 | Re: [HACKERS] Here it is - view permissions] |
Previous Message | Andrew Martin | 1998-02-23 13:09:43 | Re: [HACKERS] libpgtcl undefined symbol error with pgaccess-0.76 |