On 8 November 2012 08:33, Dean Rasheed <dean.a.rasheed@gmail.com> wrote:
> OK, yes I think we do need to be throwing the error at runtime rather
> than at plan time. That's pretty easy if we just keep the current
> error message...
Oh wait, that's nonsense (not enough caffeine). The rewrite code needs
to know whether there are INSTEAD OF triggers before it decides
whether it's going to substitute the base relation. The fundamental
problem is that the plans with and without triggers are completely
different, and there's no way the executor is going to notice the
addition of triggers if they weren't there when the query was
rewritten and planned.
Regards,
Dean