[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [GENERAL] problem with triggers
From:       Scott Marlowe <scott.marlowe () gmail ! com>
Date:       2010-01-31 23:55:59
Message-ID: dcc563d11001311555k20d93dadnf93234df6bb7bf77 () mail ! gmail ! com
[Download RAW message or body]

On Sun, Jan 31, 2010 at 4:53 PM, Florent THOMAS <mailinglist@tdeo.fr> wrote:
> Hy everybody,
>
> I have a problem with 2 triggers.
>
> I work on 3 tables :
> table A ==> with one trigger after insert that insert values in table B
> Table B ==> with one trigger after insert that insert values in table C
> Table C
> As I insert values on table A, I have a message that indicates the EXECUTE
> statement as null.
> I wonder if it is because the 2nd insert is sent as the first one is not
> ended.
> In this case, how configure postgresql to accept this second insertion?

OK, that's a good overview, but it would help if you had a simple
self-contained test case to post so we could reproduce what you're
seeing.

-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
[prev in list] [next in list] [prev in thread] [next in thread]