From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | Jan Wieck <jwieck(at)debis(dot)com> |
Cc: | PostgreSQL HACKERS <pgsql-hackers(at)postgreSQL(dot)org>, PostgreSQL PATCHES <pgsql-patches(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] Here it is - view permissions |
Date: | 1998-02-24 03:18:39 |
Message-ID: | Pine.BSF.3.96.980223231732.230C-100000@thelab.hub.org |
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...
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 1998-02-24 03:25:09 | Re: [HACKERS] Re: Appended a string of text to each line in a file |
Previous Message | Vadim B. Mikheev | 1998-02-24 03:01:57 | Re: [HACKERS] How To free resources used by large object Relations? |