Integrity constraint checking in stratified databases
Journal of Logic Programming
Foundations of semantic query optimization for deductive databases
Foundations of deductive databases and logic programming
ACM Transactions on Database Systems (TODS)
A slick procedure for integrity checking in deductive databases
Proceedings of the eleventh international conference on Logic programming
Integrity constraints: semantics and applications
Logics for databases and information systems
Materialized views: techniques, implementations, and applications
Materialized views: techniques, implementations, and applications
Three types of redundancy in integrity checking: an optimal solution
Data & Knowledge Engineering
Logic, Programming, and PROLOG
Logic, Programming, and PROLOG
Database Systems: The Complete Book
Database Systems: The Complete Book
Deriving Production Rules for Constraint Maintainance
VLDB '90 Proceedings of the 16th International Conference on Very Large Data Bases
Translating advanced integrity checking technology to SQL
Database integrity
Revisiting and improving a result on integrity preservation by concurrent transactions
OTM'10 Proceedings of the 2010 international conference on On the move to meaningful internet systems
| Hi-index | 0.00 |
Database integrity constraints, understood as logical conditions that must hold for any database state, are not fully supported by current database technology. It is typically up to the database designer and application programmer to enforce integrity via triggers or tests at the application level, which are difficult to maintain and error prone. Two important aspects must be taken care of. 1. It is too time consuming to check integrity constraints from scratch after each update, so simplified checks before each update should be used relying on the assumption that the current state is consistent. 2. In concurrent database systems, besides the traditional correctness criterion, the execution schedule must ensure that the different transactions can overlap in time without destroying the consistency requirements tested by other, concurrent transactions. We show in this paper how to apply a method for incremental integrity checking to automatically extend update transactions with locks and simplified consistency tests on the locked elements. All schedules produced in this way are conflict serializable and preserve consistency in an optimized way.