Re: PL/SQL question

From: Jeff Eckermann <jeff_eckermann(at)yahoo(dot)com>
To: Mike Nolan <nolan(at)gw(dot)tssi(dot)com>, "Froggy / Froggy Corp(dot)" <froggy(at)froggycorp(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: PL/SQL question
Date: 2004-04-21 20:25:07
Message-ID: 20040421202507.57904.qmail@web20809.mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

--- Mike Nolan <nolan(at)gw(dot)tssi(dot)com> wrote:
> > In fact the problem seems to come from the
> "INSERT INTO". I delete
> > everything from the function and only keep the
> "INSERT INTO" and get the
> > same problem.
>
> Given that this is supposed to be a trigger
> function, what's
> your 'create trigger' statement look like?
>
> Part of the problem may be how your 'return null' is
> being handled,

AFAIK, returning null from a trigger function causes
the whole operation (insert, update or delete) to be
aborted, so the transaction is rolled back, including
the insert inside the function. You want to return
NEW instead.

> and that can be related to when the trigger fires.
> --
> Mike Nolan
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 8: explain analyze is your friend



__________________________________
Do you Yahoo!?
Yahoo! Photos: High-quality 4x6 digital prints for 25
http://photos.yahoo.com/ph/print_splash

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Karsten Hilbert 2004-04-21 20:26:51 Re: ident authentication problem
Previous Message Mike Mascari 2004-04-21 20:20:07 Re: [OT] Tom's/Marc's spam filters?