Postgres Pro
Downloads
Home   >   mailing lists

Re: Row insertion w/ trigger to another table update causes row insertion to _not_ occur - Mailing list pgsql-general

From Ow Mun Heng
Subject Re: Row insertion w/ trigger to another table update causes row insertion to _not_ occur
Date
Msg-id D1109E8B2FB53A45BDB60F8145905CE902DB3D81@wdmyexbe03.my.asia.wdc.com
Whole thread Raw
In response to Re: Row insertion w/ trigger to another table update causes row insertion to _not_ occur  (Greg Stark <gsstark@mit.edu>)
Responses Re: Row insertion w/ trigger to another table update causes row insertion to _not_ occur
List pgsql-general
Tree view 
-----Original Message-----
From: gsstark@gmail.com [mailto:gsstark@gmail.com] On Behalf Of Greg Stark
>> On Tue, Jul 21, 2009 at 11:25 PM, Ow Mun Heng<ow.mun.heng@wdc.com> wrote:
>>    RETURN NULL;


> From the docs:
> "It can return NULL to skip the operation for the current row."
> -- http://www.postgresql.org/docs/current/static/trigger-definition.html

> Just make your trigger return NEW and it won't kill the insert to the
> child table.

Dang it.. I just re-read the online docs this morning and I missed it.
Then again, since I'm new to triggers, I may have mis-interpreted that.

Thanks for it. I'll give it a go.

pgsql-general by date:

Previous
From: Greg Stark
Date:
Subject: Re: Row insertion w/ trigger to another table update causes row insertion to _not_ occur
Next
From: Aleksander Kmetec
Date:
Subject: Inserts into sl_log tables timing out (related to the dataloss bug)