Re: Cascade Trigger Not Firing - Mailing list pgsql-general

From Ron
Subject Re: Cascade Trigger Not Firing
Date
Msg-id 5bbfe578-6f0a-0f33-b9ef-01ac4eb0c811@gmail.com
Whole thread Raw
In response to Re: Cascade Trigger Not Firing  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On 9/14/19 9:54 AM, Tom Lane wrote:
[snip
The only mention of this feature in 38.1 "Overview of Trigger Behavior"
is 
   UPDATE triggers can moreover be set to fire only if certain columns   are mentioned in the SET clause of the UPDATE statement.

which seems to me to be plenty specific enough --- it is carefully
*not* saying that the trigger will fire if the column changes value.
The CREATE TRIGGER man page never says that, either.

Given that the UPDATE "*can* ... be set to fire only if certain columns are mentioned in the SET clause of the UPDATE statement", it logically follows that the default behavior is something else (for example, if the field value changes for whatever reason.

--
Angular momentum makes the world go 'round.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Cascade Trigger Not Firing
Next
From: stan
Date:
Subject: Can I wrtie a function that has a BEFORE trigger that is not columnname dpendent?