>
> 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@candle.pha.pa.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)