Transactional Editing of File-Backed Database Tables
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
It is challenging to enable transactional editing of file-backed tables within a database with a concurrency control mechanism, especially when files are write-once only and cannot be modified in-place.
Innovation Solution
Implementing a file-backed table as a logical view of disk files connected with metadata, where metadata is stored in a platform database with a concurrency control mechanism, allowing edits by creating new files and updating metadata within database transactions, supporting any file format and concurrency control technique.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If files are stored as write-once only in a database, then data integrity and concurrency control are improved, but the ability to perform in-place modifications is lost
Solution Approach 1:
The patent implements copying by creating new file versions when modifications are needed. Instead of modifying files in-place, the system creates new files with the updated content and updates the metadata to point to the new version. This resolves the contradiction by maintaining write-once integrity while enabling modifications through copy-and-replace operations.
Solution Approach 2:
The patent applies preliminary action by pre-creating new file versions before finalizing the modification. The system prepares new files with updated content in advance, then atomically swaps the metadata references. This ensures that concurrency control mechanisms can manage versions effectively while maintaining the write-once constraint.
2Extent of automation
If metadata is stored in a platform database with concurrency control, then transactional editing capability is improved, but device complexity increases
Solution Approach 1:
The patent uses metadata as an intermediary between the file storage system and the concurrency control mechanism. The metadata layer abstracts the complexity of concurrency control from the actual file operations, allowing transactional editing without directly managing file-level locking and concurrency. This resolves the contradiction by introducing a manageable abstraction layer.
Solution Approach 2:
The patent applies universality by making the metadata table serve multiple functions: it stores file location information, manages versioning, enforces concurrency control, and enables transactional operations. This multi-functionality reduces the need for separate specialized components, thereby managing complexity while achieving automated transactional editing.
3Reliability
If new files are created for each modification, then write-once constraint is satisfied, but storage space and write operations increase
Solution Approach 1:
The patent applies discarding and recovering by deleting old file versions after they are no longer needed, while recovering the metadata references to point to new versions. The system maintains a clean-up mechanism that removes obsolete file data, preventing unlimited accumulation of versions. This resolves the contradiction by satisfying write-once constraints while managing storage space through selective deletion.
Data Source
AI summary
Systems and methods for editing a file-backed table in a database having a concurrency control mechanism, that include reading the content of the file-backed table, and modifying the content of the file-backed table.