Database Replay via Modification History
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems fail to efficiently copy a read-only database table to a writable database, record updates, and replay those updates when the original read-only database table changes, requiring manual script updates and maintenance.
Innovation Solution
A method that detects triggers, obtains updated data from a read-only table, stores it in a modifiable table, retrieves a comprehensive and persistent modification history, and applies these modifications to the updated data, allowing for automatic replay without manual script updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If manual scripting tools are used to copy and update database tables, then flexibility in applying custom changes is achieved, but maintenance complexity and time consumption increase significantly
Solution Approach 1:
The patent creates a copy of the read-only database table (modifiable table) that can be automatically updated. When changes are made to the read-only table, the system automatically copies those changes to the modifiable table, eliminating the need to manually update scripts while maintaining flexibility in applying custom changes through the modification history mechanism.
Solution Approach 2:
The system performs self-updating by automatically detecting changes in the read-only table and applying them to the modifiable table through recorded modification histories. This self-service mechanism eliminates manual intervention in the update process, significantly reducing maintenance time while preserving adaptability.
2Adaptability or versatility
If read-only database tables are copied to writable databases, then data customization is enabled, but synchronization complexity increases when original data changes
Solution Approach 1:
The system performs preliminary action by recording all modifications to the modifiable table in a modification history before the next synchronization. When the read-only table is updated, the system retrieves the recorded modification history and applies those changes in advance, ensuring synchronization without complex real-time coordination.
Solution Approach 2:
The modification history acts as an intermediary mechanism between the read-only and modifiable tables. It stores the changes made to the modifiable table and enables automatic replay of those changes when the source table is updated, simplifying the synchronization process while maintaining data customization capabilities.
3Productivity
If database updates are recorded and replayed automatically, then operational efficiency improves, but system complexity and data management overhead increase
Solution Approach 1:
The patent extracts the modification history from the main database table structure, storing it as a separate record that tracks changes. This extraction allows the system to maintain operational efficiency through automatic replay while isolating the complexity of change tracking from the core data storage mechanism, making the system more manageable.
Data Source
AI summary
A system and method for providing database replay are disclosed. In one embodiment, the system detects a trigger; obtains updated data from a read-only table; stores the updated data in a modifiable table; retrieves a modification history including a comprehensive and persistent record of the changes made to one or more earlier versions of the modifiable table; and applies the modifications indicated in the modification history to the updated data stored in the modifiable table.