From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | scrappy(at)hub(dot)org (The Hermit Hacker) |
Cc: | jwieck(at)debis(dot)com, pgsql-hackers(at)postgreSQL(dot)org, pgsql-patches(at)postgreSQL(dot)org |
Subject: | Re: [PATCHES] Re: [HACKERS] Here it is - view permissions |
Date: | 1998-02-24 03:50:12 |
Message-ID: | 199802240350.WAA19509@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
> On Fri, 20 Feb 1998, Jan Wieck wrote:
>
> > First step done,
> >
> > below is the patch to have views to override the permission
> > checks for the accessed tables. Now we can do the following:
> >
> > CREATE VIEW db_user AS SELECT
> > usename,
> > usesysid,
> > usecreatedb,
> > usetrace,
> > usecatupd,
> > '**********'::text as passwd,
> > valuntil
> > FROM pg_user;
>
> I used the rewrite RULE here, instead of the above VIEW, with the
> VIEW being merely a 'SELECT * FROM pg_user'...by using the RULE (unless
> I'm mistaken?), if we change pg_user (ie. add another field at some later
> date), the view itself shouldn't require a change...
I thought we couldn't use rules because COPY will dump out the password,
no?
--
Bruce Momjian | 830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1998-02-24 03:51:51 | Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/bin/initdb initdb.sh' |
Previous Message | Vadim B. Mikheev | 1998-02-24 03:39:57 | Re: [HACKERS] regression: select_views.sql |