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 D1109E8B2FB53A45BDB60F8145905CE902DB3F8C@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  (Sim Zacks <sim@compulab.co.il>)
List pgsql-general

> From: Sim Zacks [mailto:sim@compulab.co.il]

>-----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;
>
>Just make your trigger return NEW and it won't kill the insert to the
>child table.

>>I agree that is certainly one problem, but in any case an After Update
>>trigger would have worked.

I actually did try that, it didn't work. (I thought I mentioned that in the
original email. Oh well..)

Have yet to try the NEW method though

pgsql-general by date:

Previous
From: Sim Zacks
Date:
Subject: Re: Row insertion w/ trigger to another table update causes row insertion to _not_ occur
Next
From: Chris Spotts
Date:
Subject: Re: array_agg crash?