Writable Shared Database Objects via Converter Pages
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional database-driven systems face inefficiencies due to duplicative storage of static data across multiple database instances, which is unnecessary and requires recreation when adding new environments, and lack transparent write access to shared database objects imported from a provider database.
Innovation Solution
Implementing a system where reader database instances can access and modify shared database objects from a provider database instance without affecting the original data, using converter pages and cache mechanisms to manage page and block addresses, allowing transparent write access while maintaining data integrity across instances.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If shared database objects are imported from a provider database to reader databases, then data duplication is reduced and storage efficiency is improved, but write access to the shared objects becomes restricted and complex
Solution Approach 1:
The patent introduces a conversion layer that mediates between reader database write requests and provider database object structure. The converter receives write requests for shared objects, converts them into appropriate operations, and applies them to the provider database while maintaining the illusion of direct write access for the reader application.
Solution Approach 2:
The patent segments the database object into two distinct parts: shared components stored in the provider database and local components stored in the reader database. This segmentation allows read operations to access the shared portion efficiently while write operations can modify either the shared portion (through conversion) or local portion (directly), resolving the write access complexity.
2Adaptability or versatility
If static data is duplicated across multiple database instances, then each instance has independent access and modification capability, but storage efficiency decreases and data must be recreated when adding new environments
Solution Approach 1:
The patent merges the shared static data portion into a single provider database instance, eliminating duplication across multiple reader databases. This combining approach maintains storage efficiency while preserving independent access capability through the conversion layer that handles write requests for the shared objects.
3Ease of operation
If write access is implemented to shared database objects, then application transparency is improved, but data integrity across multiple reader databases may be compromised
Solution Approach 1:
The converter acts as an intermediary that ensures data integrity by controlling all write access to shared objects. It converts write requests into operations that affect only the provider database or creates local copies in the reader database, preventing unintended side effects on other reader databases while maintaining application transparency.
Solution Approach 2:
The patent applies local quality by allowing different parts of the database object to have different accessibility characteristics. The shared portion maintains read-only integrity across reader databases, while local portions allow independent write access. This differentiation preserves data integrity for shared data while providing write capability where needed.
Data Source
AI summary
A system may include a provider database, a reader database, and a database management system. The provider database may include a provider data area having a plurality of provider block addresses, and the reader database may include a reader data area having a plurality of reader block addresses, and a mapping of provider-specific identifiers to block addresses of the plurality of provider data pages and of reader-specific identifiers to block addresses of the plurality of reader data pages. The database management system may modify a database object of the reader database, the object being is associated with a provider-specific identifier; and modify the mapping to map the provider-specific identifier to a first block address of one of the plurality of reader data pages.