From: | Wijnand Wiersma <wwiersma(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Triggers after a rule |
Date: | 2005-09-28 09:44:09 |
Message-ID: | fb4cc2420509280244487336a0@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi list,
I am currently trying to give normal users some read access to some
tables in the database. I also need to give update access to one
column of one table.
I have the table contact, the user should not be able to read or
update anything in it, except for his own record. So I created the
view v_my_account. When the user selects * from it he only sees his
own record. That works great. I also made a rule:
CREATE RULE update_v_my_account AS ON UPDATE TO v_my_account
DO INSTEAD
UPDATE contact set pause=NEW.pause where username=USER;
This does not work since there are some triggers on the contact table
and the trigger function selects the contact table and I don't want to
give the user access to that.
I thought that when a rule is applied the triggers which are triggerd
would also have the same userid as the rule query, but I was wrong.
Does anyone know a nice workaround?
Wijnand
(I hope I was clear enough)
From | Date | Subject | |
---|---|---|---|
Next Message | Janning Vygen | 2005-09-28 09:50:53 | Re: ERROR: type "temp_gc" already exists |
Previous Message | Martijn van Oosterhout | 2005-09-28 09:44:03 | Re: postgresql and C++/C |