A. Kretschmer <andreas.kretsch...@schollglas.com> wrote: > In response to Igor Neyman : > > > > > > CREATE TRIGGER tafter > > > AFTER INSERT OR UPDATE > > > ON r.m_a > > > FOR EACH ROW > > > EXECUTE PROCEDURE r.m_t(); > > > > > > > > > > Trigger function for an insert/update trigger should return "NEW", not > > NULL (OLD - for "on delete" trigger): > > It's an AFTER TRIGGER, so the RETURN-Value ignored.
According the doc: The return value of a BEFORE or AFTER statement-level trigger or an AFTER row-level trigger is always ignored; it might as well be null. http://www.postgresql.org/docs/current/static/plpgsql-trigger.html Andreas -- Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect. (Linus Torvalds) "If I was god, I would recompile penguin with --enable-fly." (unknown) Kaufbach, Saxony, Germany, Europe. N 51.05082°, E 13.56889° -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
