Buffering data records which are read once increases the performance when these data records are accessed again. In 3.0, it was only possible to buffer data if it was read directly with a table.
If the data was accessed from the application program using a view, it was not possible to buffer the data, that is the data was read from the database again each time the data was accessed.
In 4.0 it is now possible to buffer data read with a view.
Analogously to tables, technical settings can now be defined for views as well.
In the technical settings of a view you can define if data read with the view should be buffered and how this should be done. The same aspects as for tables are valid for the final decision whether the data of a view should be buffered.
The technical settings of a view behave like the corresponding settings for tables.
Keep in mind that the buffer of a view is invalidated if the data of its base tables changes.
Maintenance of the technical settings of a view is optional. If the technical settings are not maintained, the data read with the view is not buffered.
Buffering is only possible for database views. Buffering is meaningless for the other view types.