Repairing and Querying Databases under Aggregate Constraints
Research has deeply investigated several issues related to the use of integrity constraints on relational databases. In particular, a great deal of attention has been devoted to the problem of extracting "reliable" information from databases containing pi
- PDF / 1,060,128 Bytes
- 66 Pages / 439.37 x 666.14 pts Page_size
- 110 Downloads / 256 Views
For further volumes: http://www.springer.com/series/10028
Sergio Flesca • Filippo Furfaro • Francesco Parisi
Repairing and Querying Databases under Aggregate Constraints
Sergio Flesca Dipartimento di Elettronica Informatica e Sistemistica Università della Calabria Rende Italy [email protected]
Filippo Furfaro Dipartimento di Elettronica Informatica e Sistemistica Università della Calabria Rende Italy
Francesco Parisi Dipartimento di Elettronica Informatica e Sistemistica Università della Calabria Rende Italy
e-ISSN 2191-5776 ISSN 2191-5768 e-ISBN 978-1-4614-1641-8 ISBN 978-1-4614-1640-1 DOI 10.1007/978-1-4614-1641-8 Springer New York Dordrecht Heidelberg London Library of Congress Control Number: 2011938682 © The Author(s) 2011 All rights reserved. This work may not be translated or copied in whole or in part without the written permission of the publisher (Springer Science+Business Media, LLC, 233 Spring Street, New York, NY 10013, USA), except for brief excerpts in connection with reviews or scholarly analysis. Use in connection with any form of information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed is forbidden. The use in this publication of trade names, trademarks, service marks, and similar terms, even if they are not identified as such, is not to be taken as an expression of opinion as to whether or not they are subject to proprietary rights. Printed on acid-free paper Springer is part of Springer Science+Business Media (www.springer.com)
Preface
It is a common belief that databases and knowledge bases should be completely free of inconsistency. As a matter of fact, commercial database management systems avoid any inconsistency by aborting updates or transactions yielding to an integrity constraint violation. However, this approach for handling inconsistency cannot be adopted in the contexts where knowledge from multiple sources is integrated (such as in the contexts of data warehousing, database integration and automated reasoning systems), since the source giving rise to integrity constraint violation is not clearly identifiable. A new approach for dealing with inconsistency in contexts such as database integration is that of “accepting” it and providing appropriate mechanisms to handle inconsistent data. The process achieving a consistent state in a database with respect to a given set of integrity constraints can be considered as a separate process that can be executed after that inconsistency has been detected. In other words, the key idea to handle inconsistency is to live with an inconsistent database, and modify query semantics in order to obtain only answers representing consistent information. Most of the previous work in this area addressed the problem of extracting consistent information from databases violating “classical” forms of constraint (such as keys, foreign keys, functional dependencies). In this manuscript, we focus on databases where the stored data violate a particular form of
Data Loading...
