1991
DOI: 10.1007/3-540-55015-1_26
|View full text |Cite
|
Sign up to set email alerts
|

On the efficient computation of the difference between consecutive database states

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
2

Citation Types

0
27
0

Year Published

1992
1992
2009
2009

Publication Types

Select...
5
1

Relationship

0
6

Authors

Journals

citations
Cited by 54 publications
(27 citation statements)
references
References 21 publications
0
27
0
Order By: Relevance
“…Our approach, for query evaluation rather than for constraint checking, differs in storing previous derived relations and in transforming the programs used in query evaluation. [4,25]. The goal of this approach is to efficiently compute the standard model of a stratified database after a database update.…”
Section: Semi-naive Evaluationmentioning
confidence: 99%
See 3 more Smart Citations
“…Our approach, for query evaluation rather than for constraint checking, differs in storing previous derived relations and in transforming the programs used in query evaluation. [4,25]. The goal of this approach is to efficiently compute the standard model of a stratified database after a database update.…”
Section: Semi-naive Evaluationmentioning
confidence: 99%
“…It is similar to our approach in using the previous standard model (analogous to our stored relations) to simplify the task of computing the standard model (query answer) after the update. Our approach differs by storing intermediate relations rather than reasons (or "supports") for including computed facts [4], by not using meta-programs to compute the difference between successive models [25], and by transforming the programs used in query evaluation. Our approach is, however, more restricted as it does not allow negation in rules and queries.…”
Section: Semi-naive Evaluationmentioning
confidence: 99%
See 2 more Smart Citations
“…Many previous approaches [3,6,7,8,12,13,14,15] consider that the information of a Data Warehouse System consists of a set of materialized views that store information from one or more databases that the organization uses in its operational systems. The process of loading this information is usually done using daily batch processes at night in order to avoid the slowdown of the operation systems.…”
Section: Introductionmentioning
confidence: 99%