Daniel Rail wrote:

>Here's a message from Dmitry Yemanov dated Nov 7, 2003, on the
>Firebird-Devel group:
>
>"I'm going to disable the current "feature" when a view can be updatable both
>directly and via the trigger. This situation is an anomaly which may cause
>server crashes/bugchecks. I suggest the following strong rules:
>
> 1) tables are always updatable
> 2) views with triggers are always updatable
> 3) views without triggers are updateable only when the well-known
>conditions are true (non-union, single table, no aggregates)
>
>Notes:
>
> - Computed fields are non-updatable in all cases but the item 2 above.
> - A view with triggers is considered updatable for operation X if it has
>at least one BEFORE- or AFTER-X triggers."
>
>You can follow the thread on that group.
>

That was the original, and I believe correct, behavior.

>
>
>