Re: basic trigger using OLD not working?

From: Rick Casey <rick(dot)casey(at)colorado(dot)edu>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: basic trigger using OLD not working?
Date: 2005-02-24 22:50:47
Message-ID: 421E5A47.4050406@colorado.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks much! That met with partial success; but getting closer.

The error message about OLD went away (thankfully!), but there is still
no data from the OLD variable. Here is the code again:

create trigger PEDIGREES_hist_del_trig
AFTER DELETE
on PEDIGREES
FOR EACH ROW
EXECUTE PROCEDURE logPedigreesDel();

CREATE OR REPLACE FUNCTION logPedigreesDel() RETURNS TRIGGER AS '
begin
RAISE EXCEPTION ''OLD.famindid = '', OLD.famindid;
return OLD;
end;
' LANGUAGE plpgsql;

Which when it fires results in:
cgb_lab_data=# \i testphdtrig.sql
psql:testphdtrig.sql:1: ERROR: OLD.famindid =

Regards,
rick

Tom Lane wrote:

>Rick Casey <rick(dot)casey(at)colorado(dot)edu> writes:
>
>
>>Here is the code that creates the delete trigger:
>>create trigger PEDIGREES_hist_del_trig
>>AFTER DELETE
>>on PEDIGREES
>>EXECUTE PROCEDURE logPedigreesDel();
>>
>>
>
>I think you forgot FOR EACH ROW. By default, the above creates a
>STATEMENT trigger, in which you don't have access to individual rows.
>
> regards, tom lane
>
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron Mayer 2005-02-24 23:08:34 Re: [PATCHES] A way to let Vacuum warn if FSM settings are low.
Previous Message Ron Mayer 2005-02-24 22:43:45 Re: [PATCHES] A way to let Vacuum warn if FSM settings are low.