| From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Cascade Trigger Not Firing |
| Date: | 2019-09-14 15:00:18 |
| Message-ID: | 5bbfe578-6f0a-0f33-b9ef-01ac4eb0c811@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | stan | 2019-09-14 18:33:50 | Can I wrtie a function that has a BEFORE trigger that is not column name dpendent? |
| Previous Message | Tom Lane | 2019-09-14 14:54:45 | Re: Cascade Trigger Not Firing |