Re: Precedence of a TRIGGER vs. a CHECK on a column

On Sun, 11 Jan 2004, ezra epstein wrote:
> So it seems that the CHECK definied for the non_empty_name domain is being
> applied before the trigger is executed.  Yet, it seems that NON NULL
> constraints are applied after triggers get called.

I think it's that your domain constraint is being applied before the
trigger is executed and that the table constraints are being applied
after given that I get the same behavior with a domain constraint of not
null.  This makes sense (although I haven't checking the spec wording)
since the value is being coerced into the domain in order to be put into
the row that's being passed to the trigger (thus triggering the domain
constraints).