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

From Sim Zacks
Subject Re: Row insertion w/ trigger to another table update causes row insertion to _not_ occur
Date
Msg-id 4A669A94.1050008@compulab.co.il
Whole thread Raw
In response to Re: Row insertion w/ trigger to another table update causes row insertion to _not_ occur  ("Ow Mun Heng" <ow.mun.heng@wdc.com>)
Responses Re: Row insertion w/ trigger to another table update causes row insertion to _not_ occur
List pgsql-general
<p style="margin-bottom: 0cm; margin-top: 0pt;">Ow Mun Heng wrote:<br /><blockquote
cite="mid:D1109E8B2FB53A45BDB60F8145905CE902DB3D81@wdmyexbe03.my.asia.wdc.com"type="cite"><pre wrap="">-----Original
Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:gsstark@gmail.com">gsstark@gmail.com</a> [<a
class="moz-txt-link-freetext"href="mailto:gsstark@gmail.com">mailto:gsstark@gmail.com</a>] On Behalf Of Greg Stark
</pre><blockquotetype="cite"><blockquote type="cite"><pre wrap="">On Tue, Jul 21, 2009 at 11:25 PM, Ow Mun Heng<a
class="moz-txt-link-rfc2396E"href="mailto:ow.mun.heng@wdc.com"><ow.mun.heng@wdc.com></a> wrote:
 
   RETURN NULL;     </pre></blockquote></blockquote><blockquote type="cite"><pre wrap="">Just make your trigger return
NEWand it won't kill the insert to the
 
child table.   </pre></blockquote><pre wrap="">
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.</pre></blockquote> I agree that is certainly one problem, but in any case an After
Updatetrigger would have worked.<br /> 

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Inserts into sl_log tables timing out (related to the dataloss bug)
Next
From: "Ow Mun Heng"
Date:
Subject: Re: Row insertion w/ trigger to another table update causes row insertion to _not_ occur