From: | "Oberpriller, Wade D(dot)" <oberpwd(at)nsc-msg01(dot)network(dot)com> |
---|---|
To: | "PostgreSQL General Help (E-mail)" <pgsql-general(at)postgresql(dot)org> |
Subject: | Triggers/Rules that insert/update other tables and permissions |
Date: | 2002-06-18 17:06:31 |
Message-ID: | 5B7014A44B89494E830AD32859FBC85802B38644@nsc-msg01.network.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello,
I have a schema like so:
Table1 is read-only to PUBLIC;
Table2 is hidden completely from PUBLIC;
View1 is a writable view derived from Table1;
If a user other than the super-user writes to View1, rules are triggered to
actually write to Table1 and this works fine. However, if I add a
rule/trigger on Table1, so that whenever Table1 is written to, Table2 will
be written to, I get a permissions error when I try to write to View1.
Do I have to make Table2 accessable, shouldn't the permissions be passed on
like a setuid program?
Wade Oberpriller http://www.storagetek.com
Software Development Phone: (763) 424-1538
StorageTek: MRDC (800) 328-9108 ext. 1538
wade_oberpriller(at)storagetek(dot)com Fax: (763) 391-1095
From | Date | Subject | |
---|---|---|---|
Next Message | Jason Earl | 2002-06-18 17:09:03 | Re: db grows and grows |
Previous Message | Gordon Luk | 2002-06-18 16:53:54 | Re: Help, could not input Chinese text in Version 7.2.1 !!! |