Database View Update Translation via Segmented Data Instances
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing relational database management systems face difficulties in translating view updates in a side-effect free manner, particularly for views with join attributes, and struggle to maintain the integrity of subviews during view deletions.
Innovation Solution
The technique separates the data instance of a view into a logical and physical instance, using identifiers to manage queries, insertions, deletions, and updates in base tables, ensuring that view updates are propagated without affecting other subviews or introducing additional tuples.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If view updates are translated to base table updates, then view maintenance is achieved, but side-effects affect other subviews and data integrity is compromised
Solution Approach 1:
The patent segments the view data instance into logical and physical components, separating the view definition from the base table data. This allows updates to be applied locally to the physical data without propagating side-effects to other subviews, as each subview can independently manage its own data instance.
Solution Approach 2:
The patent introduces a mediator mechanism that translates view updates into base table updates while filtering out side-effects. The mediator ensures that only the specific tuples intended for update are modified, preventing unintended effects on other subviews and maintaining data integrity.
2Reliability
If view deletions are processed, then view maintenance is achieved, but subview instances are affected and data integrity is compromised
Solution Approach 1:
The patent segments the view data instance into logical and physical components, allowing deletions to be applied locally to the physical data without affecting other subview instances. Each subview maintains its own independent data instance, preventing cascade deletions.
Solution Approach 2:
The mediator mechanism translates view deletions into base table deletions while preserving subview instances. The mediator ensures that only the specific tuples intended for deletion are removed, preventing unintended effects on other subviews.
3Reliability
If identifiers are associated with data values, then side-effect free translation is achieved, but system complexity increases
Solution Approach 1:
The patent creates a copy of the base table data as the physical data instance, separate from the original base table. This copy includes identifiers associated with data values, allowing updates to be applied without affecting the original base table or other subviews, while managing complexity through structured duplication.
Data Source
AI summary
A method and system are disclosed that allow database views and base tables to be treated identically with respect to queries, insertions, deletions and updates. The method and system include separating the data instance of a view into a logical data instance and a physical data instance. The physical data instance is extended to include identifiers on data values that are used to query insert, delete and update information in base tables. The manner in which users and applications interface with the view remains unchanged since those interactions occur at the logical level.