AFTER triggers & RETURN - Mailing list pgsql-hackers

From Robert Haas
Subject AFTER triggers & RETURN
Date
Msg-id 603c8f070911051334mc368e27me2dd5e086ea86a27@mail.gmail.com
Whole thread Raw
Responses Re: AFTER triggers & RETURN
List pgsql-hackers
Tom's recent work to fix the (TG_OP = 'INSERT' and NEW.foo ...)
problem reminded me of another PL/pgsql annoyance:

create table foo (a integer);
create or replace function broken() returns trigger as $$begin perform
1; end$$ language plpgsql;
create trigger bar after insert on foo for each row execute procedure broken();
insert into foo values (1);
ERROR:  control reached end of trigger procedure without RETURN
CONTEXT:  PL/pgSQL function "broken"

Since the return value is ignored anyway, why do we have to complain
if it's left out altogether?  Granted, it's easy to work around, but
still.

...Robert


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Why do OLD and NEW have special internal names?
Next
From: Andrew Dunstan
Date:
Subject: Re: AFTER triggers & RETURN