Skip to end of metadata
Go to start of metadata

Any view may be marked as updatable. In many circumstances the view definition may allow the view to be inherently updatable without the need to manually define a trigger to handle INSERT/UPDATE/DELETE operations.

An inherently updatable view cannot be defined with a query that has:

  • A set operation (INTERSECT, EXCEPT, UNION).
  • Aggregation (aggregate functions, GROUP BY, HAVING)
  • A LIMIT clause

A UNION ALL can define an inherently updatable view only if each of the UNION branches is itself inherently updatable. A view defined by a UNION ALL can support inherent INSERTs if it is a Federated Optimizations#Partitioned Union and the INSERT specifies values that belong to a single partition.

Any view column that is not mapped directly to a column is not updatable and cannot be targeted by an UPDATE set clause or be an INSERT column.

If a view is defined by a join query or has a WITH clause it may still be inherently updatable. However in these situations there are further restrictions and the resulting query plan may execute multiple statements. For a non-simple query to be updatable, it is required:

If the default handling is not available or you wish to have an alternative implementation of an INSERT/UPDATE/DELETE, then you may use Update Procedures (Triggers) to define procedures to handle the respective operations.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Jan 12, 2016

    Should the verbiage of "TRIGGER" be used to describe implementing custom INSERT/UPDATE/DELETE? Since this is related to using the ALTER TRIGGER statement to update what's defined. Maybe change the title include TRIGGER, example "Updatable View Triggers"

    1. Jan 12, 2016

      The main reason we use both trigger and update procedure terminology is that Designer was in many places still using the latter. Just go ahead and make whatever edit you want and it can be refined from there.