Reactive consistency control in deductive databases

Abstract

Classical treatment of consistency violations is to back out a database operation or transaction.In applications with large numbers of fairly complex consistency constraints this clearly is an unsatisfactory solution. Instead, if a violation is detected the user should be given a diagnosis of the constraints that failed, a line of reasoning on the cause that could have led to the violation, and suggestions for a repair. The problem is particularly complicated in a deductive database system where failures may be due to an inferred condition rather than simply a stored fact, but the repair can only be applied to the underlying facts. The paper presents a system which provides automated support in such situations. It concentrates on the concepts and ideas underlying the approach and an appropriate system architecture and user guidance, and sketches some of the heuristics used to gain in performance.

Consistency management with repair actions

“…In [14], a system is described that generates actions from closed, range-restricted first order logic formulae. The repair algorithm can automatically find repairs for violated existential formulae without user intervention.…”

Dynamic integrity constraints definition and enforcement in databases: a classification framework

“…The methods developed by Decker (1986), Kowalski et al (1987), Lloyd et al (1987), Moerkotte and Lockemann (1991), Wuthrich (1993), Pastor and Olive (1994), Asirelli et al (1996), Lee and Ling (1996) deal with deductive databases. In the area of object-oriented databases we can refer the works of Jeusfeld and Jarke (1991), Palopoli and Torlone (1992), Siebes and Van der Voort (1992), Karadimce and Urban (1993).…”

“…Some integrity checking methods are described by Hsu and Imielinski (1985), Kowalski et al (1987), Lloyd et al (1987), Bry et al (1988), Urban and Delcambre (1990), Bertino et al (1997). The works presented by Ceri and Widom (1990), Moerkotte and Lockemann (1991), Palopoli and Torlone (1992), Karadimce and Urban (1993), Wuthrich (1993), Ceri et al (1994b) are integrity maintenance methods.…”

“…Some methods with run-time approach are Kowalski et al (1987), Moerkotte and Lockemann (1991), Palopoli and Torlone (1992), Wuthrich (1993), Teniente and Olive (1995). Examples of compile-time methods are Ceri and Widom (1990), Wallace (1991), Ceri et al (1994b), Pastor and Olive (1994), Widom et al (1994).…”

Consistency preserving updates in deductive databases

“…Some of them [KM90,Wüt93,TO95,Dec97] consider view updating and integrity constraint maintenance without imposing significant restrictions on the integrity constraints they can handle. Other methods either impose significant restrictions on the constraints they can deal with, like [CHM95,CST95,LT97]; consider an integrity constraint checking approach [GL90] or do not tackle the view updating problem at all [ML91,CFPT94,Ger94,Maa98,Sch98]. However, most of these methods present important limitations regarding correctness and completeness.…”