Automatic generation of production rules for integrity maintenance
ACM Transactions on Database Systems (TODS)
A survey of database design transformations based on the Entity-Relationship model
Data & Knowledge Engineering
An execution model for limited ambiguity rules and its application to derived data update
ACM Transactions on Database Systems (TODS)
Consistency enforcement in entity-relationship and object-oriented models
Data & Knowledge Engineering - Special issue on ER '97
Improving database design through the analysis of relationships
ACM Transactions on Database Systems (TODS)
Oracle8 PL/SQL Programming
Practical Applications of Triggers and Constraints: Success and Lingering Issues (10-Year Award)
VLDB '00 Proceedings of the 26th International Conference on Very Large Data Bases
Deriving Production Rules for Constraint Maintainance
VLDB '90 Proceedings of the 16th International Conference on Very Large Data Bases
Constraints in Object-Oriented Analysis
Proceedings of the First JSSST International Symposium on Object Technologies for Advanced Software
On Formalizing the UML Object Constraint Language OCL
ER '98 Proceedings of the 17th International Conference on Conceptual Modeling
ER'00 Proceedings of the 19th international conference on Conceptual modeling
| Hi-index | 0.00 |
The specification of data integrity controls in DBMS, and particularly support for triggers, is one of the most important features for database developers and administrators. However, it is recognized that the specification of a correct set of triggers is a difficult and error-prone task. Our proposal aims to facilitate such a task by suggesting a different method for determining constraints and triggers that check constraints when database updates take place. Specifically, the method proposes to define trigger templates in order to enforce constraints imposed in a schema pattern and to store them in a database. When the analyst specifies a particular conceptual schema (which matches the schema pattern) the associated triggers are automatically generated from the information stored in the trigger template database.