mlsanityData to 14 Oct 2026

All-Instances Restricted Chase Termination

arXiv 1901.03897 ↗First posted 12 Jan 2019cs.DB cs.LOcited by 2

Not on the map. Why?

Abstract (arXiv)

The chase procedure is a fundamental algorithmic tool in database theory with a variety of applications. A key problem concerning the chase procedure is all-instances termination: for a given set of tuple-generating dependencies (TGDs), is it the case that the chase terminates for every input database? In view of the fact that this problem is undecidable, it is natural to ask whether known well-behaved classes of TGDs ensure decidability. We consider here the main paradigms that led to robust TGD-based formalisms, that is, guardedness and stickiness. Although all-instances termination is well-understood for the oblivious version of the chase, the more subtle case of the restricted (a.k.a. the standard) chase is rather unexplored. We show that all-instances restricted chase termination for guarded and sticky single-head TGDs is decidable.

Key facts. Cited by 2 papers in the map (data through 14 Oct 2026). First posted on arXiv 12 Jan 2019.

Builds on

No reference list yet.

Built on by

Cited by year

Citing papers per year: 2022: 2.

2 papers.