Samuel Gilbert <samuel(dot)gilbert(at)ec(dot)gc(dot)ca> writes:
> Here is a complete example demonstrating the issue I am encountering :
What seems to be happening is:
1. The parent table has a NOT NULL constraint on modificationDate.
2. parent_dispatcher_trigger does RETURN NEW, so the tuple will be
inserted into the parent table as well as the selected child (presumably
this is not what you wanted ...)
3. There is no trigger that will replace the modificationDate for an
insertion into the parent. So the parent insertion fails, after all
the triggers have run.
regards, tom lane