ACM Home Page
Please provide us with feedback. Feedback
On propagation of deletions and annotations through views
Full text PdfPdf (177 KB)
Source Symposium on Principles of Database Systems archive
Proceedings of the twenty-first ACM SIGMOD-SIGACT-SIGART symposium on Principles of database systems table of contents
Madison, Wisconsin
SESSION: Research session 5: views and warehousing table of contents
Pages: 150 - 158  
Year of Publication: 2002
ISBN:1-58113-507-6
Authors
Peter Buneman  University of Edinburgh and University of Pennsylvania
Sanjeev Khanna  University of Pennsylvania
Wang-Chiew Tan  University of Pennsylvania
Sponsors
SIGART: ACM Special Interest Group on Artificial Intelligence
SIGMOD: ACM Special Interest Group on Management of Data
SIGACT: ACM Special Interest Group on Algorithms and Computation Theory
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 7,   Downloads (12 Months): 44,   Citation Count: 19
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/543613.543633
What is a DOI?

ABSTRACT

We study two classes of view update problems in relational databases. We are given a source database S, a monotone query Q, and the view Q(S) generated by the query. The first problem that we consider is the classical view deletion problem where we wish to identify a minimal set T of tuples in S whose deletion will eliminate a given tuple t from the view. We study the complexity of optimizing two natural objectives in this setting, namely, find T to minimize the side-effects on the view, and the source, respectively. For both objective functions, we show a dichotomy in the complexity. Interestingly, the problem is either in P or is NP-hard, for queries in the same class in either objective function.The second problem in our study is the annotation placement problem. Suppose we annotate an attribute of a tuple in S. The rules for carrying the annotation forward through a query are easily stated. On the other hand, suppose we annotate an attribute of a tuple in the view Q(S), what annotation(s) in S will cause this annotation to appear in the view, minimizing the propagation to other attributes in Q(S)? View annotation is becoming an increasingly useful method of communicating meta-data among users of shared scientific data sets, and to our knowledge, there has been no formal study of this problem.Our study of these problems gives us important insights into computational issues involved in data provenance or lineage --- the process by which data moves through databases. We show that the two problems correspond to two fundamentally distinct notions of provenance, why and where-provenance.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

1
 
2
 
3
D. Maier and L. Delcambre. Superimposed Information for the Internet. In Proceedings of the Int'l Workshop on Web and Databases (WebDB), pages 1-9, 1999.
4
 
5
E. M. Gold. Complexity of automatic identification of given data, 1974. Unpublished manuscript.
 
6
 
7
8
 
9
Lincoln Stein. Distributed Annotation Server. http://biodas.org.
10
11
12
 
13
W3C. Annotea Project. http://www.w3.org/2001/Annotea.
 
14
Y. Cui and J. Widom. Run-Time Translation of View Tuple Deletions Using Data Lineage. Technical report, Stanford University, 2001. http://dbpubs.stanford.edu:8090/pub/2001-24.
15

CITED BY  19

Collaborative Colleagues:
Peter Buneman: colleagues
Sanjeev Khanna: colleagues
Wang-Chiew Tan: colleagues