Selective Database Journal Flushing for Asymmetric Encryption
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In asymmetric database environments where data is stored encrypted with separate keys, the database manager cannot always flush the journal, leading to inefficiencies and increased error likelihood due to the need for decryption, which is not possible in non-interactive modes.
Innovation Solution
Implementing a partial journal flushing mechanism in non-interactive modes by bypassing decryption-dependent entries and transforming multiple journal entries for the same record into a single request, allowing for selective flushing of journal entries that do not require decryption, and combining create and delete requests while postponing modification requests until interactive mode.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the database manager waits until a predetermined number of journal entries are reached before flushing the entire journal, then flushing efficiency is improved, but the journal size increases which decreases efficiency and increases error likelihood
Solution Approach 1:
The patent divides the journal flushing process into segments by identifying and separating flushable entries (those not requiring decryption) from non-flushable entries (those requiring decryption). This allows the database manager to flush available entries immediately rather than waiting for a predetermined number, thereby maintaining high flushing efficiency while keeping the journal size manageable.
Solution Approach 2:
The patent applies partial action by flushing only the subset of journal entries that can be processed in non-interactive mode (i.e., entries not requiring decryption). This partial flushing approach prevents the journal from growing too large while still making progress on committing changes, resolving the contradiction between flushing efficiency and journal size management.
2Ease of operation
If the database manager flushes the entire journal as a single task, then the operation is simplified, but error likelihood increases and efficiency decreases when decryption is required
Solution Approach 1:
The patent segments the journal into flushable and non-flushable portions, allowing the database manager to process flushable entries independently without attempting decryption. This segmentation maintains operational simplicity for the flushable portion while eliminating decryption-related errors, thereby improving reliability without significantly complicating the flushing operation.
Solution Approach 2:
The patent extracts and separates entries requiring decryption from those not requiring decryption. By taking out the problematic decryption-dependent entries and handling them separately (in interactive mode), the system reduces error likelihood while maintaining the simplicity of bulk flushing for the remaining entries.
3Productivity
If the database manager attempts to flush entries requiring decryption in non-interactive mode, then all journal entries can be processed, but the system encounters errors due to inability to decrypt
Solution Approach 1:
The patent segments journal entries into two categories: those processable in non-interactive mode and those requiring interactive mode. This segmentation allows the system to process the maximum number of entries in non-interactive mode without encountering decryption errors, while deferring decryption-dependent entries to interactive mode where errors can be avoided.
Solution Approach 2:
The patent applies partial action by processing only the subset of entries that can be flushed without decryption in non-interactive mode. This approach accepts that not all entries will be processed in a single non-interactive flush, but it eliminates errors by avoiding decryption attempts, thereby improving reliability while maintaining reasonable productivity.
Data Source
AI summary
In one embodiment, entries in a database journal in a non-interactive mode can be partially flushed to maintain database performance. In particular, data records that require decryption prior to flushing a database journal entry can be bypassed in non-interactive mode, while data records that need not be decrypted can be flushed. For example, entries that relate to a creation or deletion of a data record can be performed, while entries relating to modification of an existing record can be bypassed and processed during an interactive mode of operation. Other embodiments also include a transformation of the database journal using a filter so that multiple entries to a same record can be combined.