Inserts with Database Views

Inserts with Database Views

If a database view is created with a single transparent table, it is possible to maintain the data of the table using this view. The behavior when inserting a record for a field of the table which is not contained in the view depends on whether NULL values are permitted for this field:

If the field is defined on the database as NOT NULL with an initial value, the field is filled with the corresponding initial value.

If the field is defined on the database as NOT NULL without an initial value, an insert is not possible. Such an action results in a database error.

If the field is not defined on the database as NOT NULL, there will be a NULL value in this field.

For this reason you should not maintain any records in a table with database views if an initial value is not defined for the field, i.e. the field is not defined as NOT NULL with initial values (see Initial Values). Changing records which are already in the table with a database view is not critical if the database view contains all the key fields of the table.

When a table is maintained with a projection view, the initial values for the fields not contained in the view are automatically filled in.

See also:

Database Views

Projection Views