Deriving Relationships between Integrity Constraints for Schema Comparison.pdf

Deriving Relationships between Integrity Constraints for Schema Comparison.pdf

  1. 1、本文档共12页,可阅读全部内容。
  2. 2、原创力文档(book118)网站文档一经付费(服务费),不意味着购买了该文档的版权,仅供个人/单位学习、研究之用,不得用于商业用途,未经授权,严禁复制、发行、汇编、翻译或者网络传播等,侵权必究。
  3. 3、本站所有内容均由合作方或网友上传,本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺!文档内容仅供研究参考,付费前请自行鉴别。如您付费,意味着您自己接受本站规则且自行承担风险,本站不退款、不进行额外附加服务;查看《如何避免下载的几个坑》。如果您已付费下载过本站文档,您可以点击 这里二次下载
  4. 4、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等,请点击“版权申诉”(推荐),也可以打举报电话:400-050-0827(电话支持时间:9:00-18:30)。
查看更多
Deriving Relationships between Integrity Constraints for Schema Comparison

Deriving Relationships between IntegrityConstraints for Schema ComparisonCan Turker and Gunter SaakeOtto-von-Guericke-Universitat MagdeburgInstitut fur Technische und Betriebliche InformationssystemePostfach 4120, D{39016 Magdeburg, Germanyftuerkerjsaakeg@iti.cs.uni-magdeburg.de To appear in: W. Litwin, T. Morzy and G. Vossen, editors, Second East-EuropeanSymposium on Advances in Databases and Information Systems (ADBIS98),September 8-11, 1998, Poznan, Poland, LNCS, Springer-Verlag, Berlin, 1998. Abstract. Schema comparison is essential for integrating di erentdatabase schemata. Since the semantics of a schema is also representedby its integrity constraints, they must be considered by a correct schemacomparison method. Especially the extensional relationships betweenclasses are determined by the relationship between the correspondingintegrity constraint sets. In this paper, we work out the relationships be-tween di erent types of integrity constraints. As a result, we present rulesfor comparing integrity constraint sets. These rules can be used after aschema conforming step, where naming, type and structural con icts aresolved, to exactly x the extensional relationship between object classes.1 IntroductionSchema integration [1] is one of the central issues in logically integrating databasesystems [6]. Schema integration aims at deriving an integrated schema which isa virtual view on all database classes to be integrated. Traditionally, all existingschema integration methods, e.g. [4, 7, 3, 2, 5], assume that the database designer{ as integrator { is an expert of the application domain who has complete know-ledge about the semantics of the schemata to be integrated. Thus, the databasedesigner should be able to exactly de ne the extensional relationship betweentwo classes of di erent schemata in the schema comparison step. Obviously, thisis a very hard task for the database designer.A key point which is not regarded by the existing integration approaches isthe cor

文档评论(0)

l215322 + 关注
实名认证
内容提供者

该用户很懒,什么也没介绍

1亿VIP精品文档

相关文档