Improving integrity constraint checking for stratified deductive databases

Lee, Sin Yeung; Ling, Tok Wang

doi:10.1007/3-540-58435-8_225

Cited by 17 publications

(18 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…UTIC is sound, but, in general, methods that are uncertainty-intolerant (i.e., not uncertainty-tolerant, e.g., those in [26,28]) are unsound, as shown below.…”

Section: Methods That Are Uncertainty-intolerantmentioning

confidence: 99%

Capturing and Scaling Up Concurrent Transactions in Uncertain Databases

Cuzzocrea

Decker

Muñoz-Escoí

2013

Advanced Techniques for Knowledge Engineering and Innovative Applications

View full text Add to dashboard Cite

This chapter provides a complete framework for capturing and scaling-up concurrent transactions over uncertain databases. Models and methods proposed in the context of this framework for managing data uncertainty are innovative as previous studies have not considered the specific case of concurrent transactions, which may worse the uncertainty of database management activities beyond to the simplest case of isolated transactions. Indeed, as this chapter demonstrates, inconsistency tolerance of integrity management, constraint checking and repairing easily scale up to concurrent transactions in a natural way, and query answers in concurrent transactions over uncertain data remain certain in the presence of uncertainty. This analytical contribution is enriched by means of a reference architecture for uncertain database management under concurrent transactions that strictly adheres to models and methods that are the main contributions of this research.

show abstract

“…UTIC is sound, but, in general, methods that are uncertainty-intolerant (i.e., not uncertainty-tolerant, e.g., those in [26,28]) are unsound, as shown below.…”

Section: Methods That Are Uncertainty-intolerantmentioning

confidence: 99%

Capturing and Scaling Up Concurrent Transactions in Uncertain Databases

Cuzzocrea

Decker

Muñoz-Escoí

2013

Advanced Techniques for Knowledge Engineering and Innovative Applications

View full text Add to dashboard Cite

show abstract

“…Several approaches to simplification do not comply with this requirement [16,11,18,4,6,19,10]; [19] showed that his II method was more efficient than [11,18] and we gave evidence of great improvements obtained with Simp wrt II. Methods that as ours, are based on pre-tests are, e.g., [17,9]. However, the former does not allow more than one update action in a transaction to operate on the same relation; furthermore, no mechanism corresponding to parameters is present, thus requiring to execute the procedure for each specific update.…”

Section: More On Related Workmentioning

confidence: 99%

Incremental Integrity Checking: Limitations and Possibilities

Christiansen

Martinenghi

2005

Logic for Programming, Artificial Intelligence, and Reasoning

View full text Add to dashboard Cite

Abstract. Integrity checking is an essential means for the preservation of the intended semantics of a deductive database. Incrementality is the only feasible approach to checking and can be obtained with respect to given update patterns by exploiting query optimization techniques. By reducing the problem to query containment, we show that no procedure exists that always returns the best incremental test (aka simplification of integrity constraints), and this according to any reasonable criterion measuring the checking effort. In spite of this theoretical limitation, we develop an effective procedure allowing general parametric updates that, for given database classes, returns ideal simplifications and also applies to recursive databases. Finally, we point out the improvements with respect to previous methods based on an experimental evaluation.

show abstract

“…This information could allow us to detect and select, as soon as possible, such conditions that would not be repaired in any case. Moreover, we are thinking about considering a more clever marking of the graph by incorporating techniques like those proposed in [LS93,LL96] to determine whether a condition could be actually affected by a repair.…”

Section: Conclusion and Further Workmentioning

confidence: 99%

Consistency preserving updates in deductive databases

Mayol

Teniente

2003

Data & Knowledge Engineering

View full text Add to dashboard Cite

Several problems may arise when a deductive database is updated. The problems that are addressed in this paper are those of integrity constraint maintenance and view updating. In this sense, we define a method that tackles both problems in an integrated way and that it is sound and complete. We also propose an architecture for our method to deal with both problems efficiently. Improvement of efficiency during the integrity constraint maintenance is based on

show abstract

Improving integrity constraint checking for stratified deductive databases

Cited by 17 publications

References 4 publications

Capturing and Scaling Up Concurrent Transactions in Uncertain Databases

Capturing and Scaling Up Concurrent Transactions in Uncertain Databases

Incremental Integrity Checking: Limitations and Possibilities

Consistency preserving updates in deductive databases

Contact Info

Product

Resources

About