Maintaining materialized views without accessing base data (Q1115648)
From MaRDI portal
| This is the item page for this Wikibase entity, intended for internal use and editing purposes. Please use this page instead for the normal view: Maintaining materialized views without accessing base data |
scientific article; zbMATH DE number 4087079
| Language | Label | Description | Also known as |
|---|---|---|---|
| English | Maintaining materialized views without accessing base data |
scientific article; zbMATH DE number 4087079 |
Statements
Maintaining materialized views without accessing base data (English)
0 references
1988
0 references
Access to a database through a user view can be serviced quickly when the view is materialized, i.e., the transformed data is explicitly stored. In the presence of database updates, however, the materialized view can be come costly to maintain, often it must be completely rederived from the base data using the view definition. Under some conditions the view can be updated directly given only the view definition, the current contents of the materialized view, and the update operation (still expressed against the base data), without accessing the base data itself. We consider relational views defined by projection, selection, and join. We present necessary and sufficient conditions on the view definition, contents, and update operations for insertions and deletions to be reflected in the view without reference to base data. Because the possibility of such view-based updating is dependent on the current contents of view, we call the update conditionally autonomously computable.
0 references
relational databases
0 references
query processing
0 references
conceptual relations
0 references
stored relations
0 references
pre-joined relations
0 references
derived relations
0 references
snapshots
0 references
database updates
0 references
materialized view
0 references