| From: | Mattias Kregert <matti(at)algonet(dot)se> |
|---|---|
| To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Here it is - view permissions |
| Date: | 1998-02-23 10:32:04 |
| Message-ID: | 34F15024.7146F2F6@algonet.se |
| 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?
/* m */
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brett McCormick | 1998-02-23 10:41:45 | Re: pl/{perl, pgsql} (was Re: AW: [HACKERS] triggers, views and rules (not instead)) |
| Previous Message | Jan Wieck | 1998-02-23 09:41:12 | Re: pl/{perl, pgsql} (was Re: AW: [HACKERS] triggers, views and rules (not instead)) |