From: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
---|---|
To: | "Matthias Schmidt" <schmidtm(at)mock-software(dot)de> |
Cc: | "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Allow GRANT/REVOKE permissions to be applied to all schema objects with one command |
Date: | 2005-01-27 13:42:19 |
Message-ID: | 6EE64EF3AB31D5448D0007DD34EEB3412A75EB@Herge.rcsinc.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> TODO1: Allow GRANT/REVOKE permissions to be applied to all schema
> objects with one command.
> TODO2: Assign Permissions to schemas wich get automatically inherited
> by objects created in the schema.
>
> a) should we pursue both of them?
> b) how can a syntax for TODO1 look like? Anchored at 'GRANT ... ON
> SCHEMA' or 'GRANT ... ON <objecttype>' ?
I vote no on a. Reason: it's relatively easy to do the same thing
already. However if you do end up doing that, I'd suggest using
'CASCADE'. This is reasonably consistent with other dependency honoring
commands in pg.
What I would really like to see is TODO2: because this allows greater
flexibility for controlling security. This is impossible in pg
currently, and may be a slightly more sophisticated job.
Good luck!
Merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-01-27 14:24:11 | Re: Deferrable Unique Constraints |
Previous Message | Robert Treat | 2005-01-27 13:39:31 | Re: Patent issues and 8.1 |