Frank van Vugt <[EMAIL PROTECTED]> writes:
>> It might also work for you to do this with access rights.
> Well, actually that's kinda how it's working at the moment, however I would
> rather avoid this additional dependancy on user/role since it's really
> field/situation-dependent (see below).
After reading the explanation, this seems way too specialized a
situation to make a good argument that we need a general feature
of the sort.
You can get to where you need to be by passing an indicator in
the trigger arguments, eg,
CREATE TRIGGER ... BEFORE UPDATE ... EXECUTE PROCEDURE mytrigger(0);
CREATE TRIGGER ... AFTER UPDATE ... EXECUTE PROCEDURE mytrigger(1);
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
