The Prolog not-predicate and negation as failure rule
New Generation Computing
Deriving production rules for constraint maintenance
Proceedings of the sixteenth international conference on Very large databases
Compile-Time and Runtime Analysis of Active Behaviors
IEEE Transactions on Knowledge and Data Engineering
A Path Removing Technique for Detecting Trigger Termination
EDBT '98 Proceedings of the 6th International Conference on Extending Database Technology: Advances in Database Technology
Run-time Detection of Non-Terminating Active Rule Systems
DOOD '95 Proceedings of the Fourth International Conference on Deductive and Object-Oriented Databases
ICDE '96 Proceedings of the Twelfth International Conference on Data Engineering
Unrolling Cycles to Decide Trigger Termination
VLDB '99 Proceedings of the 25th International Conference on Very Large Data Bases
Further Improvements on Integrity Constraint Checking for Stratifiable Deductive Databases
VLDB '96 Proceedings of the 22th International Conference on Very Large Data Bases
Improving Rule Analysis by Means of Triggering and Activation Graphs
RIDS '95 Proceedings of the Second International Workshop on Rules in Database Systems
Refined Termination Decision in Active Databases
DEXA '97 Proceedings of the 8th International Conference on Database and Expert Systems Applications
Modeling and verifying DML triggers using event-B
ACIIDS'13 Proceedings of the 5th Asian conference on Intelligent Information and Database Systems - Volume Part II
| Hi-index | 0.01 |
One of the major applications of trigger rules is to maintain database integrity. However, since trigger rules, like computer programs, may not be written correctly, it is important to have tools to verify the correctness. Generally, this is an undecidable problem. Only few works exist on this problem. However, most of these works either depend on human inspection, or incur a run-time overhead. In this paper, we introduce a new approach which does not depend on any human judgment nor any run-time monitoring. The trigger rules we are checking are those trigger rules which update object properties but do not insert any new object nor destroy an existing object. The constraints in our paper do not have any existential quantifier. If our method returns "yes", we can guarantee that the set of trigger rules are written correctly to enforce the given constraint.