Re: IF- statements in a rule's 'DO INSTEAD SELECT ...'- statement - Mailing list pgsql-general

From Bertin, Philippe
Subject Re: IF- statements in a rule's 'DO INSTEAD SELECT ...'- statement
Date
Msg-id B9E404D03707D511BD4D00105A40C10466B590@wevmex01.barco.com
Whole thread Raw
In response to IF- statements in a rule's 'DO INSTEAD SELECT ...'- statement  ("Bertin, Philippe" <philippe.bertin@barco.com>)
Responses Re: IF- statements in a rule's 'DO INSTEAD SELECT ...'- statement  (Alvaro Herrera <alvherre@atentus.com>)
List pgsql-general
Hi Alvaro, Hi Nigel,

Thanks for your reply. I indeed already tried with a plpgsql function. But
that's just my problem : if I call a function from within a view's rule,
this function is not executed anymore with the same rights as a user had on
the view. So if a user may access a view, but not the table behind, calling
a function in the DO INSTEAD- clause will not execute the function with the
proper (view) rights on the table ...

(to all) Could anyone - (developers, eventually ?) explain me why the
(security) context of a function call is not passed along when the function
gets called from within a view ? I think this feature is for sure not
superfluous, and I could consider having a look into the code to have this
changed (but I think this is a VERY big pile of source codes I never ever
looked at before, so this would take a lot of efforts ... for me)

Kind regards,

Philippe Bertin.


pgsql-general by date:

Previous
From: "Tille, Andreas"
Date:
Subject: Allow user to create tables
Next
From: jon@univits.se
Date:
Subject: SQLData, PostgreSQL and typemap woes