A new method for integrity constraint checking in deductive databases
Integrity signals
Registry
Cites
Statistics
Claims the paper makes
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
The main concern of [84] is to show why using inconsistency indicators instead of integrity constraints is relevant for efficiency and a good idea in general.
“(the main concern of [84] is to show why using inconsistency indicators instead of integrity constraints is relevant for efficiency and a good idea in general).”
From Creating specialised integrity checks through partial evaluation of meta-interpreters (1998) · cites this paper as [84]
For a lot of examples, such as databases with a large number of facts, concentrating on potential updates leads to very good efficiency.
“For a lot of examples, like databases with a large number of facts, this leads to very good efficiency (see, e.g., the experiments in [16,84]).”
From Creating specialised integrity checks through partial evaluation of meta-interpreters (1998) · cites this paper as [84]
The approaches of [90,84] are more limited in some important respects and both use ad hoc techniques with meta-interpreters and partial deduction.
“Their approaches are, however, more limited in some important respects and both use ad hoc techniques n sdda e e a a a meta-interpreters and partial deduction”
From Creating specialised integrity checks through partial evaluation of meta-interpreters (1998) · cites this paper as [84]
Refs. [90,84] both explicitly address this compilation aspect.
“Refs. [90,84] both explicitly address this compilation aspect.”
From Creating specialised integrity checks through partial evaluation of meta-interpreters (1998) · cites this paper as [84]
Cites
Sterling, L., Shapiro, E., & Garrett, R. (1987) · IEEE Expert · doi:10.1109/mex.1987.4307074 · Cited by 1,101 · see citing works
Flagged first, then by citations
Cited by
Sorted by citations
Creating specialised integrity checks through partial evaluation of meta-interpreters
Leuschel, M., & De Schreye, D. (1998) · The Journal of Logic Programming · doi:10.1016/s0743-1066(97)10012-7 · Cited by 29 · see citing works
- Authors
- Seljée, R.
- Affiliations
- Tilburg University (NL)
- Corresponding author
- Seljée, Ron
- Venue
- Data & Knowledge Engineering
- Publisher
- Elsevier BV
- Published
- 1995-03
- Volume
- 15
- Issue
- 1
- Pages
- 63-102
- ISSN
- 0169-023X (ISSN-L)
- OpenAlex
- W2127087655
- Cited by
- 14
- References
- 1
- Citations by year
- 2013: 1
- FWCI
- 4.21
- Type
- journal article
- Language
- en
- Open access
- closed
- Locations
- Data & Knowledge Engineering (publishedVersion)
- TU/e Research Portal (publishedVersion)
- TU/e Research Portal (submittedVersion)
- Topics
- Physical Sciences › Computer Science › Computer Networks and Communications › Advanced Database Systems and Queries
- Physical Sciences › Computer Science › Artificial Intelligence › Logic, Reasoning, and Knowledge
- Social Sciences › Decision Sciences › Management Science and Operations Research › Data Quality and Management
- Keywords
- integrity constraint checking, deductive databases, database consistency
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review