Representing extended entity-relationship structures in relational databases: a modular approach

A common approach to database design is to describe the structures and constraints of the database application in terms of a semantic data model, and then represent the resulting schema using the data model of a commercial database management system. Often, in practice, Extended Entity-Relationship (EER) schemas are translated into equivalent relational schemas. This translation involves different aspects: representing the EER schema using relational constructs, assigning names to relational attributes, normalization, and merging relations. Considering these aspects together, as is usually done in the design methodologies proposed in the literature, is confusing and leads to inaccurate results. We propose to treat separately these aspects and split the translation into four stages (modules) corresponding to the four aspects mentioned above. We define criteria for both evaluating the correctness of and characterizing the relationship between alternative relational representations of EER schemas.

[1]  Y. Edmund Lien,et al.  On the Equivalence of Database Models , 1982, JACM.

[2]  E. F. Codd,et al.  Extending the database relational model to capture more meaning , 1979, ACM Trans. Database Syst..

[3]  David Maier,et al.  On the foundations of the universal relation model , 1984, TODS.

[4]  Roger King,et al.  Semantic database modeling: survey, applications, and research issues , 1987, CSUR.

[5]  Richard Hull Relative Information Capacity of Simple Relational Database Schemata , 1986, SIAM J. Comput..

[6]  Lynette I. Brady A Universal Relation Assumption Based on Entities and Relationships , 1985, ER.

[7]  Toby J. Teorey,et al.  Database modeling and design: the entity-relationship approach , 1990 .

[8]  Y. Edmund Lien,et al.  On the Semantics of the Entity-Relationship Data Model , 1979, ER.

[9]  Peter P. Chen The Entity-Relationship Model: Towards a unified view of Data , 1976 .

[10]  Arie Shoshani,et al.  Name Assignment Techniques for Relational Schemas Representing Extended Entity-Relationship Schemas , 1989, ER.

[11]  Johann A. Makowsky,et al.  Identifying Extended Entity-Relationship Object Structures in Relational Schemas , 1990, IEEE Trans. Software Eng..

[12]  Sushil Jajodia,et al.  The Problem of Equivalence for Entity-Relationship Diagrams , 1983, IEEE Transactions on Software Engineering.

[13]  Paolo Atzeni,et al.  Assumptions in relational database theory , 1982, PODS '82.

[14]  David Maier,et al.  Representing Roles in Universal Scheme Interfaces , 1985, IEEE Transactions on Software Engineering.

[15]  Peter P. Chen The entity-relationship model: toward a unified view of data , 1975, VLDB '75.

[16]  T. J. Teorey,et al.  A logical design methodology for relational databases using the extended entity-relationship model , 1986, CSUR.

[17]  Victor M. Markowitz,et al.  A relation merging technique for relational databases , 1992, [1992] Eighth International Conference on Data Engineering.

[18]  Shimon Even,et al.  Graph Algorithms , 1979 .

[19]  David Maier,et al.  The Theory of Relational Databases , 1983 .

[20]  Ronald Fagin,et al.  Inclusion Dependencies and Their Interaction with Functional Dependencies , 1984, J. Comput. Syst. Sci..

[21]  Paolo Atzeni,et al.  Formal properties of net-based knowledge representation schemes , 1986, 1986 IEEE Second International Conference on Data Engineering.

[22]  V. M. Markowitz Problems underlying the use of referential integrity mechanisms in relational database management systems , 1990 .

[23]  ChenPeter Pin-Shan The entity-relationship modeltoward a unified view of data , 1976 .