>
> just to trick the engine and force the view to be only updatable by my
> triggers, not directly. There should be a better solution. Either
> a reserved
> word to make a view explicitly non-automagically updatable or a
> mechanism in
> place so when triggers are defined on a view that's already updatable, the
> "natural" behavior won't fire and only the user triggers will execute.
>

And since we're at it, what are thoughts on a slightly broader mechanism
that can do the same for normal tables (via a key word within the trigger or
something)... Some pretty nifty business rules could be built this way..

Joseph