Re: Cascade Trigger Not Firing

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: Judy Loomis <hoodie(dot)judy(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Cascade Trigger Not Firing
Date: 2019-09-14 14:54:45
Message-ID: 22653.1568472885@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
> On 9/13/19 8:07 PM, Judy Loomis wrote:
>> At the very least that note about this behavior should be highlighted,
>> probably on the Trigger Behavior page and not buried in a bunch of notes
>> on the Create Trigger page.

> I know this after the fact. Still, as a general rule the best place to
> start when learning about a command is on it's respective page under here:
> https://www.postgresql.org/docs/11/sql-commands.html
> Further I usually go to the Notes after reading the synopsis, as Notes
> is where the exceptions to the rules and gotchas are called out.

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.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron 2019-09-14 15:00:18 Re: Cascade Trigger Not Firing
Previous Message Adrian Klaver 2019-09-14 14:42:00 Re: kind of a bag of attributes in a DB . . .