> Trigger functions will now be expected to take no arguments and return
> either tuple (or trigger if we call it that) or opaque. It would also be
> sensible to allow VOID in the case of AFTER triggers, but I'm inclined not
> to do so: I think it's better that a trigger function be declared in a way
> that makes it clear it's supposed to be a trigger. If CREATE
> TRIGGER accepts
> functions returning void then I think you lose some useful error checking.
>
> Should we throw a NOTICE stating that opaque is deprecated if a trigger
> is declared with opaque? Or should we wait a release or two for that?
I think a NOTICE at creation time is fine.
> Comments?
Sounds really good.
Chris
