Selective Database Trigger Firing Through Field-Level Operation Checks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database systems incur unnecessary computational overhead due to frequent execution of database triggers, even when the trigger conditions are not met, leading to inefficient resource utilization.
Innovation Solution
Implementing database triggers with firing criteria that fire only when specific fields are not updated, using an AND combination of operated and non-operated fields, reducing unnecessary trigger executions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If database triggers are executed frequently to ensure data integrity, then reliability is improved, but computational overhead increases and system performance deteriorates
Solution Approach 1:
The patent applies preliminary action by evaluating trigger firing criteria before the actual trigger execution. The database system determines in advance whether a trigger should fire by checking if the operation affects the specified fields, preventing unnecessary trigger executions and reducing computational overhead while maintaining data integrity for relevant operations
Solution Approach 2:
The patent implements partial action by selectively firing triggers only when specific field conditions are met, rather than executing triggers for all operations. This partial execution approach reduces unnecessary computational work while ensuring reliability is maintained for operations that actually require trigger processing
2Reliability
If database triggers are executed for every operation to ensure comprehensive data validation, then reliability is improved, but resource utilization deteriorates
Solution Approach 1:
The system performs preliminary evaluation of trigger firing criteria by examining whether the database operation affects the fields specified in the trigger definition. This advance determination prevents unnecessary trigger executions and conserves computational resources while maintaining comprehensive validation for operations that require it
Solution Approach 2:
The patent extracts the trigger firing determination logic from the general trigger execution process. By separating the criteria evaluation step from the actual trigger execution, the system can identify and exclude operations that don't meet firing conditions, reducing wasted computational resources while preserving data validation reliability
3Ease of operation
If trigger firing criteria are simplified to operate on any field, then ease of operation is improved, but manufacturing precision deteriorates due to non-selective trigger execution
Solution Approach 1:
The patent applies local quality by enabling different levels of trigger field specification precision. Users can configure triggers with specific field names for precise control, or use broader field groupings for simpler configuration. The system adapts the evaluation precision to match the configuration level, maintaining ease of operation while improving execution precision through selective field matching
Data Source
AI summary
Techniques are disclosed relating to implementing database trigger firing criteria to reduce unnecessary trigger firings. In one embodiment a computer system stores trigger information relating to initiating execution of at least one trigger instruction for a database, in connection with a particular database operation specified by a database operation statement. The trigger information includes a set of one or more database field identifiers for a set of one or more fields in the database. The computer system receives a first database operation statement and makes a determination that at least one field within the set of fields is not specified by the first database operation statement. Based at least in part on the determination, the computer system initiates execution of the at least one trigger instruction.