Re: TRIGGER BEFORE INSERT

From: Adrian Klaver <aklaver(at)comcast(dot)net>
To: pgsql-general(at)postgresql(dot)org
Cc: Rafal Pietrak <rafal(at)zorro(dot)isa-geek(dot)com>, Alban Hertroys <alban(at)magproductions(dot)nl>
Subject: Re: TRIGGER BEFORE INSERT
Date: 2007-01-11 20:26:30
Message-ID: 200701111226.30559.aklaver@comcast.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thursday 11 January 2007 10:26 am, Rafal Pietrak wrote:
> On Thu, 2007-01-11 at 15:10 +0100, Alban Hertroys wrote:
> > Rafal Pietrak wrote:
> > > Hi!
> > >
> > > I'm re-posting this message again in hope someone would have a look at
> > > the case again. .. it's pending.
> >
> > You were given a solution; defer the foreign key constraint.
>
> Well. I were, but probably I'm doing something wrong with 'deferring the
> trigger'. When I put:

What previous posters have said is that you need to defer the FK. So you need
to change your table definition from:
CREATE TABLE test_utarg(tm timestamp not null, nic int, amount int not
null, dnia int references test_days(id));
to:
CREATE TABLE test_utarg(tm timestamp not null, nic int, amount int not
null, dnia int references test_days(id) INITIALLY DEFERRED);
per Toms suggestion. This eliminates the need for the SET CONSTRAINTS DEFERRED
statement.

--
Adrian Klaver
aklaver(at)comcast(dot)net

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2007-01-11 20:32:11 Re: ORDER BY col is NULL in UNION causes error?
Previous Message Alvaro Herrera 2007-01-11 20:21:50 Re: ORDER BY col is NULL in UNION causes error?