"Scott Marlowe" <[EMAIL PROTECTED]> writes:
> Since you can check which columns have changed, it's pretty easy to
> write a trigger that just skips its logic when none of the trigger
> columns have changed.
... which is pretty much the same thing a built-in implementation would
have to do, too. So it'd save you a bit of typing but nothing more.
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
