---------- Original Message -----------
From: "Dmitry Yemanov" <dimitr@...>

> Create one trigger to perform an update (i.e. insert) and another one for
> the logging. Or combine their code in the single trigger.

------- End of Original Message -------

What's the point of the engine understanding updatable views at all then? Just make all views
ignore updates, except for the side-effects of triggers. Besides, Firebird only supports a sub-set
of all possibly updatable views (many multi-table views are updatable in theory, but not in
Firebird.) At least this way anyone wanting updatable views would know there's only one way to do
them, so there'd be less confusion and fewer requests for multi-table updates. On the other hand,
Firebird could learn to do multi-table updates (all the updates that make any sense, that is,) and
the triggers for logging could instead apply to base tables that will be affected by the updates
anyway, no? What kinds of triggers would fall under neither category above (hack for multi-table
updates, triggers that could apply to the base tables)?

-Philip