Re: 36.3 Writing Tigger Functions in C

From: Dmitry Igrishin <dmitigr(at)gmail(dot)com>
To: Marko Tiikkaja <marko(at)joh(dot)to>
Cc: pgsql-docs <pgsql-docs(at)postgresql(dot)org>
Subject: Re: 36.3 Writing Tigger Functions in C
Date: 2015-08-11 11:51:28
Message-ID: CAAfz9KO5WzJY0PH0CsWCTU9W7J09CB85kQT7sZX8AOr9srxgNA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

2015-08-11 14:32 GMT+03:00 Marko Tiikkaja <marko(at)joh(dot)to>:

> On 8/11/15 12:47 PM, Dmitry Igrishin wrote:
>
>> tg_trigtuple:
>> I'm not sure why "skip the operation" is here:
>> "if you don't want to replace the row with a different one (in the
>> case of INSERT) or skip the operation"
>>
>
> Returning NULL from a row-level BEFORE trigger skips the operation which
> fired the trigger. So for an INSERT, any triggers which would otherwise
> fire after the current trigger are not fired, and the row is not INSERTed
> into the table.

Yes, but it's absolutely unclear in this place of the documentation.
Thus,
"If this trigger was fired for an INSERT or DELETE then this is what you
should return from the function if you don't want to replace the row with a
different one (in the case of INSERT) or skip the operation."
should be replaced with something like
"If this trigger was fired for an INSERT or DELETE then this is what you
should return from the function if you don't want to replace the row with a
different one (in the case of INSERT). (To skip the operation you should
return NULL.)" ?

--
// Dmitry.

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message zhangjinyu 2015-08-14 11:45:34 Re: BUG #13541: There is a visibility issue when run some DDL and Query. The time window is very shot
Previous Message Marko Tiikkaja 2015-08-11 11:32:25 Re: 36.3 Writing Tigger Functions in C