| Celma, M; García, C.; Mata, L.; Decker, H. "Comparing and Synthesising Integrity Checking Methods for Deductive Databases", Int. Conf. on Data Engineering (ICDE'94), Houston (Texas), 1994, pp. 214-222. |
....may be violated. That is, the update, together with the current content of the deductive database, may falsify some integrity constraint. The classical approach to deal with this problem has been to develop methods for checking whether a given update violates an integrity constraint (see [Oli91, CGMD94] and the references therein) When a violation is detected, the transaction is rolled back in its entirety. That is, the update request is rejected and, in this case, the user intention cannot be satisfied. We will refer to this approach as integrity checking. In some cases, this solution may not ....
....Condition, go back to the last node Cp whose condition has been repaired, restore the same marked nodes before Cp was repaired and go to Step 3 to find an alternative repair. Note that, to improve efficiency of the whole process, it will be better to use an integrity constraints checking method [Oli91, CGMD94]. Step 3: Repair a condition. Repair the condition associated to node C and include the repair into the transaction T. Notice that if the repair is a derived event, a view updating method must be applied to translate it into base events. Given the repair, compute the derived events that could be ....
Celma, M; García, C.; Mata, L.; Decker, H. "Comparing and Synthesising Integrity Checking Methods for Deductive Databases", Int. Conf. on Data Engineering (ICDE'94), Houston (Texas), 1994, pp. 214-222.
....MT95, TO92, TO95] and it could be easily adapted to be applicable to other existing methods. A different approach to enforce database consistency is integrity checking; which is concerned with developing methods for checking whether a given update violates an integrity constraint (see for example [Oli91, GCMD94]) In this case, when a violation is detected, the transaction is rejected. Both integrity constraint enforcement approaches are reasonable [Win90] The correct choice of an approach for a particular integrity constraint depends on the semantics of the integrity constraint and of the deductive ....
García, C.; Celma, M; Mota, L.; Decker, H. "Comparing and Synthesising Integrity Checking Methods for Deductive Databases", Int. Conf. on Data Engineering (ICDE'94), Houston (Texas), 1994, pp. 214-222.
....updates in deductive databases [MT95, TO95] and it could be easily adapted to other existing methods. A different approach to enforce database consistency is integrity checking; which is concerned with developing methods for checking whether a given update violates an integrity constraint [Oli91, GCMD94]. In this case, when a violation is detected, the transaction is rejected. Both integrity constraint enforcement approaches are reasonable. The correct choice of an approach for a particular integrity constraint depends on the semantics of the integrity constraint and of the deductive database. ....
García, C.; Celma, M; Mota, L.; Decker, H. "Comparing and Synthesising Integrity Checking Methods for Deductive Databases", Int. Conf. on Data Engineering (ICDE'94), Houston (Texas), 1994, pp. 214-222.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC