Data-Driven Record Filtering for Database Process Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Database administrators face lengthy and error-prone procedures when modifying processes to execute on specific records, requiring programmer intervention to change code and compile it, which can be time-consuming and prone to errors.
Innovation Solution
Implementing conditional processing based on data-driven filtering of records, where a system administrator can modify metadata to control which processes execute on records by specifying filter conditions, allowing the database system to dynamically determine which records satisfy the filter criteria and execute the appropriate processes without manual code changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a system administrator modifies process code to change which records a process executes on, then the process can be customized to execute on specific records, but the procedure becomes lengthy and error-prone requiring programmer intervention
Solution Approach 1:
The patent replaces the mechanical system of code compilation and deployment with a data-driven configuration system. Instead of modifying process code through programming tools, administrators use metadata configuration interfaces to define filter conditions. The system evaluates these conditions at runtime to determine record processing, eliminating the need for code compilation and deployment cycles.
Solution Approach 2:
The patent introduces metadata as an intermediary between the administrator's requirements and the process execution. This metadata layer acts as a mediator that translates administrative decisions into processing logic without requiring direct code modification. The metadata configuration serves as the intermediary mechanism that enables process customization while avoiding the complexities of code changes.
2Adaptability or versatility
If a system administrator modifies process code to change which records a process executes on, then the process can be customized to execute on specific records, but the procedure becomes complex and prone to errors
Solution Approach 1:
The patent replaces error-prone code modification mechanics with a data configuration mechanism. Instead of requiring programmers to write, compile, and deploy code changes, administrators configure filter conditions through metadata interfaces. This substitution eliminates compilation errors, deployment failures, and syntax errors associated with code modification.
Solution Approach 2:
The system enables administrators to self-serve process customization needs without requiring programmer intervention. The metadata configuration system provides self-contained tools for defining filter conditions and managing record selection criteria, allowing administrators to independently customize process behavior without external assistance.
3Ease of operation
If programmer intervention is required to modify process code, then precise control over process behavior can be achieved, but the complexity of the system increases
Solution Approach 1:
The patent extracts the customization logic from the process code itself and places it in separate metadata configurations. This extraction separates the filtering logic from the core process implementation, allowing administrators to modify behavior without touching the process code. The complexity of code modification is removed from the administrative workflow.
Solution Approach 2:
The patent segments the process configuration into distinct components: the core process logic and the filter conditions. This segmentation allows independent modification of filter criteria without affecting the process code. Administrators can adjust record selection by modifying only the filter metadata segment, leaving the process segment unchanged.
Data Source
AI summary
Conditional processing based on data-driven filtering of records is described. A system stores a corresponding identifier in a data structure for each of a data manipulation action, an object, a filter field, a filter condition, and a process. The system receives a request to perform the data manipulation action for the object. The system determines, for each record based on the object, whether the filter field associated with a corresponding record satisfies the filter condition. The system identifies, for each record based on the object, a corresponding record as an included record that should be included for subsequent processing in response to a determination that the filter field associated with the corresponding record either satisfies the filter condition or does not satisfy the filter condition. The system executes the process on each included record.