Bidirectional Mapping Architecture for Incremental View Maintenance
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data access solutions face challenges in efficiently managing updates across mappings, preserving data consistency, and triggering business rules, due to the complexity of updatable views and limited support for bidirectional transformations.
Innovation Solution
The ADO.NET Entity Framework introduces a novel data access architecture with a mapping architecture that uses bidirectional views for query and update processing, leveraging incremental view maintenance and materialized view maintenance algorithms to propagate updates through bidirectional views, and specifies mappings using a declarative language for well-defined semantics.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional client-side data mapping layers are used to provide updatable views, then data independence and flexibility are improved, but update processing complexity and data consistency maintenance increase
Solution Approach 1:
The patent segments the update processing into distinct phases: change detection at the application layer, change propagation through the mapping, and consistency maintenance at the database layer. This segmentation allows each component to handle updates independently, reducing overall complexity while maintaining data independence.
Solution Approach 2:
The patent introduces an intermediary mechanism that acts as a mediator between application-level changes and database-level updates. This intermediary handles the complex translation and propagation of changes through the mapping, shielding both layers from the complexity of the translation process.
2Reliability
If bidirectional transformations are implemented for query and update processing, then data consistency is improved, but system complexity and processing overhead increase
Solution Approach 1:
The patent performs preliminary actions by pre-computing and storing mapping information in a structured format. This allows bidirectional transformations to be executed efficiently at runtime without complex calculations, reducing processing overhead while maintaining data consistency.
Solution Approach 2:
The patent creates a simplified copy of the mapping structure that can be efficiently traversed during bidirectional transformations. This copy contains only the necessary mapping relationships, enabling fast query and update processing without the complexity of the full mapping system.
3Productivity
If incremental view maintenance algorithms are used to propagate updates, then update efficiency is improved, but implementation complexity and maintenance requirements increase
Solution Approach 1:
The patent merges the incremental view maintenance algorithm with the existing mapping infrastructure, combining change propagation and consistency maintenance into a unified process. This integration simplifies implementation by eliminating separate maintenance mechanisms while maintaining high update efficiency.
Solution Approach 2:
The patent implements a self-service mechanism where the system automatically detects, propagates, and maintains consistency of updates without external intervention. The incremental view maintenance algorithm operates autonomously, reducing implementation complexity by eliminating manual maintenance requirements.
Data Source
AI summary
A data access architecture is provided that includes a mapping architecture for mapping data as may be used by an application to data as persisted in a database. The mapping architecture makes use of two types of mapping views—a query view that helps in translating queries and an update view that helps in translating updates. Incremental view maintenance can be used to translate data between the application and database.