Re: Row insertion w/ trigger to another table update causes row insertion to _not_ occur

From: "Ow Mun Heng" <ow(dot)mun(dot)heng(at)wdc(dot)com>
To: "Sim Zacks" <sim(at)compulab(dot)co(dot)il>
Cc: "Greg Stark" <gsstark(at)mit(dot)edu>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: Row insertion w/ trigger to another table update causes row insertion to _not_ occur
Date: 2009-07-22 05:53:32
Message-ID: D1109E8B2FB53A45BDB60F8145905CE902DB3F8C@wdmyexbe03.my.asia.wdc.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> From: Sim Zacks [mailto:sim(at)compulab(dot)co(dot)il]

>-----Original Message-----
>From: gsstark(at)gmail(dot)com [mailto:gsstark(at)gmail(dot)com] On Behalf Of Greg Stark
>
>On Tue, Jul 21, 2009 at 11:25 PM, Ow Mun Heng<ow(dot)mun(dot)heng(at)wdc(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Chris Spotts 2009-07-22 06:18:26 Re: array_agg crash?
Previous Message Sim Zacks 2009-07-22 04:50:28 Re: Row insertion w/ trigger to another table update causes row insertion to _not_ occur