| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Thomas Hallgren <thhal(at)mailblocks(dot)com> |
| Cc: | vamsi krishna <vamsi(dot)krishnak(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Permissions within a function |
| Date: | 2004-12-17 20:26:26 |
| Message-ID: | 41C340F2.7000108@dunslane.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thomas Hallgren wrote:
> vamsi,
>
>> Why dont you create a view on the table and access the view rather
>> than the table. I guess this would resolve the issue.
>>
>> What ever select statement you want to have on the table you can make
>> it a select statement of the view. thus restricting the access to the
>> main table.
>>
>> Looking forward to hear from you.
>>
> I don't think a view would help much. I want to completely prevent the
> user from viewing or changing any data stored in the table. Using a
> view would just move the problem. Now the user must have select access
> to the view in order to call the function and that is just as bad.
>
>
Thomas,
I'm not sure if I understand exactly what you want, but would a
"security definer" function help?
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-12-17 21:24:56 | Re: Permissions within a function |
| Previous Message | Thomas Hallgren | 2004-12-17 20:15:55 | Re: Permissions within a function |