From: | Luis Sousa <llsousa(at)ualg(dot)pt> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | josh(at)agliodbs(dot)com, pgsql-sql <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: Permission on insert rules |
Date: | 2002-11-12 17:10:32 |
Message-ID: | 3DD13608.9000100@ualg.pt |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Bruce Momjian wrote:
>Josh Berkus wrote:
>
>
>>Luis,
>>
>>
>>
>>>Just a question.
>>>I'm writing some rules to insert/update some data in my database, and I
>>>gave all the privileges on that view to the user, and only select on the
>>>tables.
>>>When that user inserts data using the view, I thought that was user
>>>postgres that will do the rest ! But I got permission denied on those
>>>tables.
>>>The idea was to create a layer, with the views, giving to that user
>>>permission on views to insert and update, and not to tables.
>>>Is this possible ?
>>>
>>>
>>This is a known problem.
>>
>>I know that permissions for Functions has been addressed in 7.3. However, I
>>am not sure about permissions for updatable views. Tom, Bruce?
>>
>>
>
>Views have always had their own permissions.
>
>
>
Offcourse, but when I'm giving permissions to insert and update on
views, I have to give those permissions also to the tables !! (those
operations that are executed on rules)
Luis Sousa
From | Date | Subject | |
---|---|---|---|
Next Message | scott.marlowe | 2002-11-12 17:12:39 | Re: [SQL] Parent table has not oid? |
Previous Message | Stephan Szabo | 2002-11-12 16:30:30 | Re: Efficient ON DELETE trigger when referential integrity is |