File-Based Versioning for Serialized Database Content
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current change and transport systems in distributed computing environments face challenges in efficiently managing file-based versioning of data objects, particularly in converting serialized database content to file-based content and maintaining a change history, which hinders effective data management and collaboration across back-end systems.
Innovation Solution
The system receives a transport request with updated serialized database content, converts it to file-based content, stores it in a repository alongside a previous version, updates the database with change history, and provides a visualization of changes, enabling efficient data management and collaboration by storing and restoring transport objects as needed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If serialized database content is converted to file-based content for versioning, then data management capability is improved, but system complexity increases
Solution Approach 1:
The patent introduces a conversion layer that acts as an intermediary between the database system and the file-based versioning system. This converter translates serialized database content into file-based content formats, enabling compatibility between different data representation systems without requiring direct integration or complex bidirectional synchronization mechanisms.
Solution Approach 2:
The system creates file-based copies of database content for versioning purposes while maintaining the original database structure. This copying approach allows the versioning system to work with independent file representations, reducing the complexity of maintaining real-time synchronization between database and versioning systems.
2Loss of information
If change history is maintained in the database, then data traceability is improved, but database operation time increases
Solution Approach 1:
The patent segments the versioning functionality into a separate file-based system independent from the main database operations. By storing version information as separate files rather than database records, the system maintains complete change history without burdening the database with additional operational overhead, thus preserving traceability while minimizing impact on database performance.
3Adaptability or versatility
If multiple back-end systems access the versioning system, then collaboration capability is improved, but network communication overhead increases
Solution Approach 1:
The system provides local copies of versioned content to multiple back-end systems through the transport mechanism. Each system can access and work with local file copies, reducing the need for continuous network communication while maintaining synchronization capabilities. This approach enables collaboration by allowing systems to work independently with local copies and synchronize when needed.
Data Source
AI summary
Techniques for managing a file-based versioning of data objects include receiving, from a back-end computing system, a transport request that includes an updated transport object, the updated transport object including serialized database content of a data object; converting the serialized database content of the updated transport object to file-based content; storing the file-based content of the updated transport object in a repository over a previously-stored version of the transport object; and updating a database that includes a change history of the data object based on the storage of the file-based content in the repository.