From: | Florent THOMAS <mailinglist(at)tdeo(dot)fr> |
---|---|
To: | postgesql general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: problem with triggers |
Date: | 2010-02-01 06:39:03 |
Message-ID: | 1265006343.23250.18.camel@Dell_Inspiron |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thank you for answering so fast,
After a good night, I found the solution.
There was a problem with a variable that was name as a field name I
execute in the query.
So everything looks fine now!
Thanks a lot
Le dimanche 31 janvier 2010 à 16:55 -0700, Scott Marlowe a écrit :
> On Sun, Jan 31, 2010 at 4:53 PM, Florent THOMAS <mailinglist(at)tdeo(dot)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.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Mads Lie Jensen | 2010-02-01 07:04:58 | Re: Which version will this run on? |
Previous Message | Jayadevan M | 2010-02-01 05:40:05 | Re: how to look for duplicate rows? |