0% found this document useful (0 votes)
5 views2 pages

ER and EER To Relational Model Mapping

The document outlines the process of logical database design, focusing on the conversion of ER models to the relational model. It details the components of the relational model, including integrity constraints and various mapping techniques for entities, relationships, and ISA relationships. Learning outcomes include the ability to explain logical database design, the relational model, and the conversion process from ER to relational models.

Uploaded by

thehara001
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
5 views2 pages

ER and EER To Relational Model Mapping

The document outlines the process of logical database design, focusing on the conversion of ER models to the relational model. It details the components of the relational model, including integrity constraints and various mapping techniques for entities, relationships, and ISA relationships. Learning outcomes include the ability to explain logical database design, the relational model, and the conversion process from ER to relational models.

Uploaded by

thehara001
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

ER and EER to Relational Model Mapping

Lecture Content:

Logical database design


Relational model and its components
ER to relational mapping

Learning Outcomes:

Explain the process of logical database design.


Explain relational model and its components.
Convert a complex ER model to the relational model.

Logical Database Design

After conceptual database design, the next step is selecting a DBMS for implementation.
The conceptual design is converted into a database schema in the chosen DBMS's data
model.
Before 1970, hierarchical and network models were used.
The relational model (introduced by Codd in 1970) is now widely used.

Relational Model

Represents data simply and effectively.


A relational database consists of relations (tables).
Each relation has:
Relational schema (table structure).
Relation instance (actual data, i.e., tuples/rows).

Integrity Constraints

Domain Constraints: Values in a column must be valid according to their defined type.
Key Constraints:
A candidate key uniquely identifies tuples.
One primary key is chosen.
Referential Integrity:
Ensures foreign keys reference existing tuples in another relation.
Prevents inconsistent data.
Other Constraints:
Table constraints (e.g., account balance > 0 using CHECK in SQL).
Assertions (cross-table constraints, e.g., employee salary cannot exceed manager's
salary).

ER to Relational Model Mapping

Mapping Entities & Attributes: Convert entity attributes into relational schema.
Mapping Relationships:
Binary relationships mapped via foreign keys.
N-ary relationships require a separate relation.
Mapping ISA Relationships:
Option 1: Superclass relation + separate subclass relations.
Option 2: Only subclass relations, including superclass attributes.
Option 3: Single relation with all attributes and a type column.
Option 4: Single relation with Boolean subclass indicators.
Mapping Aggregation Relationships: Convert aggregation into relational tables, ensuring
key consistency.

Activities

Practice mapping ER diagrams to relational models.


Explore different ISA mapping techniques.
Complete the self-test questions, tutorial, and lab sheet for next week.

You might also like