Minimal-Change Integrity Maintenance Using Tuple Deletions
| dc.creator | Chomicki, Jan | |
| dc.creator | Marcinkowski, Jerzy | |
| dc.date | 2002-12-05 | |
| dc.date.accessioned | 2026-07-07T03:19:12Z | |
| dc.date.available | 2026-07-07T03:19:12Z | |
| dc.description | We address the problem of minimal-change integrity maintenance in the context of integrity constraints in relational databases. We assume that integrity-restoration actions are limited to tuple deletions. We identify two basic computational issues: repair checking (is a database instance a repair of a given database?) and consistent query answers (is a tuple an answer to a given query in every repair of a given database?). We study the computational complexity of both problems, delineating the boundary between the tractable and the intractable. We consider denial constraints, general functional and inclusion dependencies, as well as key and foreign key constraints. Our results shed light on the computational feasibility of minimal-change integrity maintenance. The tractable cases should lead to practical implementations. The intractability results highlight the inherent limitations of any integrity enforcement mechanism, e.g., triggers or referential constraint actions, as a way of performing minimal-change integrity maintenance. | |
| dc.identifier | https://arxiv.org/abs/cs/0212004 | |
| dc.identifier | http://arxiv.org/abs/cs/0212004 | |
| dc.identifier.uri | http://salesiana.dossiersoluciones.com/handle/123456789/31367 | |
| dc.subject | Databases | |
| dc.subject | H.2.3; F.4.1; I.2.3 | |
| dc.title | Minimal-Change Integrity Maintenance Using Tuple Deletions | |
| dc.type | text |