From: | PegoraroF10 <marcos(at)f10(dot)com(dot)br> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Trigger bug ? |
Date: | 2019-05-22 21:33:12 |
Message-ID: | 1558560792308-0.post@n3.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
We created a usual trigger which seemed to be not firing or not working
properly. Then we put some raise notices on it and saw that it was returning
Null values. But why, it´s after insert and is a primary key, cannot be
null.
create function MyFunction() returns trigger as $$
begin
raise '%', new.MyPK;
end$$ language plpgsql;
create trigger MyTrigger after insert on MyTable execute procedure
MyFunction();
We forgot FOR EACH ROW/STATEMENT when created our trigger.
On docs it´s written {ROW/STATEMENT} between {}, so it´s needed. But why did
it accepted our command to create that trigger ?
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2019-05-22 21:37:35 | Re: Trigger bug ? |
Previous Message | Thomas Munro | 2019-05-22 21:27:42 | Re: Centos : Load Average :OS Process Name : migration/1, migration/2 , migration/n |