"Aasmund Midttun Godal" <[EMAIL PROTECTED]> writes:
> Thank you for your quick reply!
> I understand your point of view, however the fact remains that you want the
> action to be done as though it was the DEFINER user that did it, and that
> has not changed even thoug the function itself has fin
Thank you for your quick reply!
I understand your point of view, however the fact remains that you want the
action to be done as though it was the DEFINER user that did it, and that
has not changed even thoug the function itself has finished?
regards,
aasmund.
Tom Lane writes:
"Aasmund
"Aasmund Midttun Godal" <[EMAIL PROTECTED]> writes:
> When an operation is done throug a SECURITY DEFINER style function and
> causes a trigger the current_user depends on whether it is executed BEFORE
> or AFTER. I currently run 7.3.2. I believe the BEFORE behavior is correct
> while the AFTER
I have upgraded to 7.3.4 and the problem persists.
Aasmund Midttun Godal writes:
When an operation is done throug a SECURITY DEFINER style function and
causes a trigger the current_user depends on whether it is executed BEFORE
or AFTER. I currently run 7.3.2. I believe the BEFORE behavior is
When an operation is done throug a SECURITY DEFINER style function and
causes a trigger the current_user depends on whether it is executed BEFORE
or AFTER. I currently run 7.3.2. I believe the BEFORE behavior is correct
while the AFTER behavior is wrong. A bug? already fixed?
regards,
Aasmun
