On Jan 30, 2007, at 1:17 PM, Simon Riggs wrote:
It would be even better if there was some way of not executing the
trigger at all if we knew that the UPDATE statement doesn't SET the FK
columns.


Other databases allow you to put a WHERE or CHECK clause on triggers, so that they will only fire if that evaluates to true. That would allow FK triggers to be defined as

CREATE TRIGGER ... WHERE NEW.fk != OLD.fk

and would obviously have other uses as well. Of course the question is how much time that would save vs just doing the same check in the trigger function itself.
--
Jim Nasby                                            [EMAIL PROTECTED]
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)



---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

              http://archives.postgresql.org

Reply via email to