Skip Navigation

The Computer Journal 1984 27(4):294-300; doi:10.1093/comjnl/27.4.294
© 1984 by British Computer Society
This Article
Right arrow Full Text (PDF)
Right arrow Alert me when this article is cited
Right arrow Alert me if a correction is posted
Services
Right arrow Email this article to a friend
Right arrow Similar articles in this journal
Right arrow Similar articles in ISI Web of Science
Right arrow Alert me to new issues of the journal
Right arrow Add to My Personal Archive
Right arrow Download to citation manager
Right arrow Search for citing articles in:
ISI Web of Science (1)
Right arrowRequest Permissions
Google Scholar
Right arrow Articles by Bowers, D. S.
Right arrow Search for Related Content
Social Bookmarking
 Add to CiteULike   Add to Connotea   Add to Del.icio.us  
What's this?

A Database Architecture for Aggregate-Incomplete Data

D. S. Bowers *

School of Computing Studies and Accountancy, University of East Anglia, Norwich, UK

The problem is addressed of data which are not only incomplete, but also aggregate in nature. Some difficulties associated with maintaining the consistency of such data are illustrated. These problems arise in particular when it is required that both aggregate and simple data values should be stored. An architecture is proposed for a database management system to handle this class of data, which is termed aggregate-incomplete. A generalized materialization strategy is defined on the basis of the proposed architecture, and it is shown that the consistency problems are reduced to manageable proportions.


Received May 1983.

* School of Computing Studies and Accountancy, University of East Anglia, Norwich NR4 7TJ, UK


Add to CiteULike CiteULike   Add to Connotea Connotea   Add to Del.icio.us Del.icio.us    What's this?




Disclaimer:
Please note that abstracts for content published before 1996 were created through digital scanning and may therefore not exactly replicate the text of the original print issues. All efforts have been made to ensure accuracy, but the Publisher will not be held responsible for any remaining inaccuracies. If you require any further clarification, please contact our Customer Services Department.