Something like

CREATE VIEW VIEW_NAME [NO_AUTO_UPDATES] ...

would seem like the least disrupting way to disable the behaviour.

Alternatively, it might be better if it could be something more explicit
like

CREATE VIEW VIEW_NAME [NO_AUTO_INSERT] [NO_AUTO_UPDATE] [NO_AUTO_DELETE] ...

If the extra tokens are not provided in the declaration, then the
current behaviour applies (simple queries fire both triggers and system
defaults, complex queries fire triggers and are read-only if triggers
are not provided).

Marcelo Lopez Ruiz

Ivan Prenosil wrote:

>>From: Jason Wharton
>>Another way this could be approached is to make it so that you have to
>>explicitly turn on the default view update processing.
>>
>.....
>
>>CREATE VIEW blah
>>FOR UPDATE, INSERT, DELETE
>>AS
>>BEGIN
>>....
>>
>
>I am not sure I understand you right.
>
>Are you saying that _each_ view should be read-only by default,
>unless you explicitly allow default processing ?
>It would break most existing applications and basic SQL standard conformance.
>
>Or do you mean that views _with_ triggers should be read-only
>unless you explicitly allow default processing ?
>It would also break many existing applications and seems too complicated to me.
>Just by looking at CREATE VIEW command you would not be able to say
>whether it will do default processing or not.
>
>IMO all we need is possibility to turn off default processing
>for simple views.
>
>
>Ivan
>http://www.volny.cz/iprenosil/interbase
>