Toward a uniform cause-based approach to inconsistency-tolerant database semantics
OTM'10 Proceedings of the 2010 international conference on On the move to meaningful internet systems: Part II
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
Causes of the violation of integrity constraints for supporting the quality of databases
ICCSA'11 Proceedings of the 2011 international conference on Computational science and Its applications - Volume Part V
SDKB'10 Proceedings of the 4th international conference on Semantics in data and knowledge bases
Inconsistency-tolerant integrity checking based on inconsistency metrics
KES'11 Proceedings of the 15th international conference on Knowledge-based and intelligent information and engineering systems - Volume Part II
Partial repairs that tolerate inconsistency
ADBIS'11 Proceedings of the 15th international conference on Advances in databases and information systems
Report on the third workshop on hot topics in software upgrades (HotSWUp'11)
ACM SIGOPS Operating Systems Review
New measures for maintaining the quality of databases
ICCSA'12 Proceedings of the 12th international conference on Computational Science and Its Applications - Volume Part IV
Managing uncertainty in databases and scaling it up to concurrent transactions
SUM'12 Proceedings of the 6th international conference on Scalable Uncertainty Management
| Hi-index | 0.00 |
All methods for efficient integrity checking require all integrity constraints to be totally satisfied, before any update is executed. However, a certain amount of inconsistency is the rule, rather than the exception in databases. In this paper, we close the gap between theory and practice of integrity checking, i.e., between the unrealistic theoretical requirement of total integrity and the practical need for inconsistency tolerance, which we define for integrity checking methods. We show that most of them can still be used to check whether updates preserve integrity, even if the current state is inconsistent. Inconsistency-tolerant integrity checking proves beneficial both for integrity preservation and query answering. Also, we show that it is useful for view updating, repairs, schema evolution, and other applications.