From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | Wijnand Wiersma <wwiersma(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Triggers after a rule |
Date: | 2005-09-28 10:06:32 |
Message-ID: | 433A6B28.8030408@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Wijnand Wiersma wrote:
> 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.
Can you show the (cut down) contents of your trigger? It's difficult to
see what you mean. I can't think of any way a trigger can provide
results to the user, so any selects within it should be safe enough.
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Patrick.FICHE | 2005-09-28 10:16:18 | Re: ERROR: type "temp_gc" already exists |
Previous Message | vdm.fbsd@virgilio.it | 2005-09-28 09:59:04 | Re: postgresql and C++/C |