Re: TODO: trigger features - Mailing list pgsql-hackers

From Tom Lane
Subject Re: TODO: trigger features
Date
Msg-id 11664.1060110293@sss.pgh.pa.us
Whole thread Raw
In response to TODO: trigger features  (Andreas Pflug <pgadmin@pse-consulting.de>)
Responses Re: TODO: trigger features
List pgsql-hackers
Andreas Pflug <pgadmin@pse-consulting.de> writes:
> - Implement a way to enable triggers to check which columns are affected 
> by the triggering statement.

This can already be done by comparing old and new values, no?

I don't have a lot of sympathy for the idea that checking what the
original UPDATE touched is a good shortcut.  Rules or previous triggers
might have changed additional columns.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: this is in plain text (row level locks)
Next
From: Andreas Pflug
Date:
Subject: Re: TODO: trigger features