Message-ID: <55C9DD49.8060706@joh.to>
Date: Tue, 11 Aug 2015 13:32:25 +0200
From: Marko Tiikkaja <marko@joh.to>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
 rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Dmitry Igrishin <dmitigr@gmail.com>,
 pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: 36.3 Writing Tigger Functions in C
References: 
 <CAAfz9KPBchVLG=MxOcD7wWiRjBQJ2CDckqC3RRYrkehy=9wedw@mail.gmail.com>
In-Reply-To: 
 <CAAfz9KPBchVLG=MxOcD7wWiRjBQJ2CDckqC3RRYrkehy=9wedw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

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.


.m


-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs