Database Lec 9 PDF

COSC 304
Introduction to Database Systems
ER to Relational Mapping
Dr. Ramon Lawrence

University of British Columbia Okanagan
ramon.lawrence@ubc.ca
COSC 304 - Dr. Ramon Lawrence
ER Model to Relational Schemas

These notes will describe how to convert an ER diagram (or
EER diagram) into a corresponding relational schema.
Conceptual database design produces a conceptual ER model.

This conceptual model is then converted into the relational
model (which is a logical model).
Note that although it is possible to design using the relational

model directly, it is normally more beneficial to perform
conceptual design using the ER model first.
Page 2
ER Model to Relational Schemas (2)

Converting an ER model to a relational database schema
involves 7 steps.
In general, these steps convert entities to relations and ER

relationships to relations. For 1:1 and 1:N relationships, foreign
keys can be used instead of separate relations.
Handling subclasses and superclasses in the EER model

requires an extra conversion step.
After conversion is performed, normalization and optimization

are often performed to improve the relational schema.
Page 3
ER Model Example
 Supervises
0..1 bonus
Supervisor
0..* Employee Department
0..1 Manages  0..1
Supervisee number {PK} number {PK}
name name
address 0..* Has 0..1
state 0..1
Has
city
street 
title
0..*
salary WorksOn  Project
1..1 0..* 0..* number {PK}

Has name
 budget
0..* location [1..3]
Dependent responsibility
name {PPK} hours
age
Page 4
Step #1: Convert Strong Entities
Step #1: Convert each strong entity to a relation.
Employee
number {PK}
name
address Employee (eno, ename, state, city, street, title, salary)
state
city
street
title
salary
Notes:
1) Attributes of the entity type become attributes of the relation.
2) Include only simple attributes in relation. For composite attributes,
only create attributes in the relation for their simple components.
3) Multi-valued attributes are handled separately (in step #6).
4) The primary key of the relation is the key attributes for the entity.
Page 5
Current Relational Schema - Step #1
Employee (eno, ename, state, city, street, title, salary)
Project (pno, pname, budget)
Department (dno, dname)
Page 6
Step #2: Convert Weak Entities
Step #2: Convert each weak entity into a relation with foreign
keys to its identifying relations (entities).
For each weak entity W with identifying owners E1, E2, …, En

create a relation R:
Identify relations R1, R2, …, Rn for entity types E1, E2, …, En.
The primary key of R consists of the primary keys of R1, R2, …,
Rn plus the partial key of the weak entity.
Create a foreign key in R to the primary key of each relation R1,
R2, …, Rn.
Attributes are converted the same as strong entities.
Page 7
Step #2: Convert Weak Entities (2)
Employee
number {PK}
name
address Employee (eno, ename, state, city, street, title, salary)
state
city
street
title
salary
1..1
Has

0..*
Dependent
name {PPK} Dependent (eno, name, age)
age
Page 8
Dependent (eno, name, age)
Employee (eno, ename, state, city, street, title, salary)
Department (dno, dname)
Page 9
Steps #3-5: Convert Relationships
Steps 3 to 5 convert binary relationships of cardinality:
1:1 - Step #3
1:N - Step #4
M:N - Step #5
Note that M:N relationships are the most general case, and the
conversion algorithm for these relationships can be applied to
1:1 and 1:N as well.
However, for performance reasons, it is normally more efficient
to perform different conversions for each relationship type.
In general, each ER relationship can be mapped to a relation.
However, for 1:1 and 1:N relationships, it is more efficient to
combine the relationship with an existing relation instead of
creating a new one.
Relationships that are not binary are handled in step #7. Page 10
Step #3: Convert 1:1 Relationships
Step #3: Convert binary 1:1 relationships into a UNIQUE foreign
key reference from one relation to the other.
Given a binary 1:1 relationship R between two entities Ei and Ej:

Identify the corresponding relations Ri and Rj.
Chose one of the relations, say Ri, and:
Add the attributes of R to Ri.
Add the primary key attributes of Rj to Ri, and create a foreign key
reference to Rj from Ri.
Declare these primary key attributes of Rj to be UNIQUE.
Notes:
You can select either Ri or Rj. Typically, it is best to select the relation that
is guaranteed to always participate in the relationship or the one that will
participate the most in the relationship.
Page 11
Step #3: Convert 1:1 Relationships (2)
Employee
number {PK} bonus
name Department
address
state number {PK}
city
0..1 Manages  0..1 name
street
title
salary Manages (eno, dno, bonus) Department (dno, dname)
Employee (eno,
ename, state, city,
street, title, salary)
Department (dno, dname, mgreno, bonus)
Note: Renamed eno to mgreno for clarity.

Page 12
Step #4: Convert 1:N Relationships
Step #4: Convert binary 1:N relationships between into a foreign
key reference from the N-side relation to the 1-side relation.
Given a binary 1:N relationship R between two entities Ei and Ej:

Let Ri be the N-side of the relation.
Add the attributes of R to Ri.
Add the primary key attributes of Rj to Ri, and create a foreign key
reference to Rj from Ri.
Notes:
Unlike 1:1 relationships, you must select the N-side of the
relationship as the relation containing the foreign key and
relationship attributes. Page 13
Employee
number {PK}
name Department
address Has
state 0..* 0..1 number {PK}
city name
street
title
salary inDept (dno, eno) Department (dno, dname, mgreno, bonus)
Employee (eno,
ename, state, city,
street, title, salary)
Employee (eno, ename, state, city, street,

title, salary, dno)
Page 14
Project
Has Department
number {PK}
name 0..* 0..1 number {PK}
budget name
location [1..3]
/totalEmp Department (dno, dname,
deptProj (dno, pno)
mgreno, bonus)
Project (pno, pname, budget, dno)
Page 15
 Supervises
0..1 Supervises (supereno, eno)
Supervisor
0..* Employee Employee (eno, ename, state, city, street,
Supervisee number {PK} title, salary, dno)
name
address
state
city
street
title Employee (eno, ename, state, city, street,
salary
title, salary, dno, supereno)
Page 16
Employee (eno, ename, state, city, street, title, salary, dno, supereno)
Page 17
Step #5: Convert M:N Relationships
Step #5: Convert binary M:N relationships into a new relation
with foreign keys to the two participating entities.
Given a binary M:N relationship between entities Ei and Ej:

Create a new relation R representing the relationship where:
R contains the relationship attributes.
The primary key of R is a composite key consisting of the primary keys of
Ri and Rj.
Add the primary key attributes of Ri and Rj to R, and create a foreign key
reference to Ri from R and to Rj from R.
Page 18
Step #5: Convert M:N Relationships
Employee WorksOn  Project
number {PK} 0..* 0..* number {PK}
name name
address budget
state location [1..3]
city
street responsibility
title hours Project (pno, pname, budget, dno)
salary
Employee (eno,
ename, state, city,
street, title, salary, WorksOn (eno, pno, resp, hours)
dno, supereno)
Page 19
WorksOn (eno, pno, resp, hours)
Page 20
Step #6: Convert Multi-Valued Attributes
Step #6: Convert a multi-valued attribute into a relation with
composite primary key consisting of the attribute value plus the
primary key of the attribute's entity.
Given a multi-valued attribute A of entity Ei:

Identify the corresponding relation Ri.
Create a new relation R representing the attribute where:
R contains the simple, single-valued attribute A.
Add the primary key attributes of Ri to R, and create a foreign key
reference to Ri from R.
The primary key of R is a composite key consisting of the primary key of
Ri and A.
Page 21
Step #6: Convert Multi-Valued Attributes
Project
number {PK}
name
budget
location [1..3]
ProjectLocation (pno, location)
Page 22
Final Relational Schema
WorksOn (eno, pno, resp, hours)
ProjectLocation (pno, location)
Page 23
Step #7: Convert n-ary Relationships
Step #7: Convert n-ary relationships by creating a new relation
to represent the relationship and creating foreign keys that
reference the related entities.
Given an n-ary relationship between entities E1, E2, …, En:

Identify relations R1, R2, …, Rn for entity types E1, E2, …, En.
Create a new relation R to represent the relationship.
The primary key of R consists of the primary keys of R1, R2, …,
Rn.
Create a foreign key in R to the primary key of each relation R1,
R2, …, Rn.
Attributes of the relationship become attributes of R.
Page 24
Step #7: Convert n-ary Relationships
quanity
price
Part Project
number {PK} number {PK}
Provide
name name
description 0..* 0..* budget
Part (pno, pname, desc) Project (jno, jname, budget)

0..*
Supplier
number {PK}
Provide (pno, sno, jno, name
qty, price) address
Supplier (sno, sname, address)
Page 25
EER to Relational Mapping

An additional step is necessary to convert subclasses and
superclasses to the relational model.
In general, we have several different approaches:

1) Create a separate relation for each superclass and subclass.
Most general technique that we will use.
2) Create relations for subclass only.
Only works if superclass has mandatory participation.
3) Create a single relation with one type attribute.
Attribute is used to indicate the type of object (subclass) in the row.
Works only if the subclasses are disjoint.
4) Create a single relation with multiple type attributes.
Have a boolean valued attribute for each subclass. True if in subclass.
Works if subclasses may be overlapping. Page 26
Step #8: Convert Subclasses
Step #8: Convert subclasses and superclasses by creating a
relation for each subclass and superclass. Link the subclasses
to the superclass using foreign key references.
Given a superclass C and set of subclasses S1, S2, …, Sn:

Create a relation R for C.
The primary key for R is the primary key of the superclass.
Create relations R1, R2, …, Rn for subclasses S1, S2, …, Sn.
The primary key for each Ri is the primary key of the superclass.
For each Ri, create a foreign key to R using the primary key
attributes.
Page 27
Step #8: Convert Subclasses
Supervisor Manager
Supervisor (eno) Manager (eno)
{Optional, AND}
Employee
number {PK}
name
address
state
city
street
title
salary
Employee (eno, ename, state, city, street, title, salary, supereno)

Page 28
Summary of
ER Model Relational Model
Entity Type Relation
1:1 or 1:N Relationship Type Foreign key (or "relationship" relation)
M:N Relationship Type "Relationship" relation and 2 foreign keys
n-ary Relationship Type "Relationship" relation and n foreign keys
Simple attribute Attribute
Composite attribute Set of simple component attributes
Multi-valued attribute Relation and foreign key
Key attribute Primary (or secondary) key
Page 29
ER to Relational Mapping Question

Question: How many of the following statements are true?
1) The M:N relationship mapping rule could be applied to 1:1

and 1:N relationships, as it is more general.
2) A weak entity will always have primary key attributes from the
identifying entity.
3) The designer has a choice on which side to put the foreign
key when mapping a 1:N relationship.
4) When mapping multi-value attributes, the table containing the
multi-value attribute will not have a composite key.
A) 0 B) 1 C) 2 D) 3 E) 4
Page 30
University Question
Page 31
TPC-H Standard Question
amount
price
Order 0..* 0..* Part

InOrder
number {PK} number {PK}
date name
totalAmount price
0..*
0..* Supplier 0..*
number {PK}
0..*
 name Supplies 
Places
0..*
In
1..1 
1..1
Customer In  Nation In  Region
number {PK} 0..* 1..1 name {PK} 0..* 1..1 name {PK}
name
Page 32
Conclusion
There is a straightforward algorithm for converting ER models
to relational schemas.
The algorithm involves 7 steps for converting regular ER

models, and 8 steps for converting EER models.
In general, these steps convert entities to relations and ER

relationships to relations. For 1:1 and 1:N relationships, foreign
keys can be used instead of separate relations.
Page 33
Objectives
Given an ER/EER diagram, be able to convert it into a
relational schema using the seven/eight steps.
Be able to discuss the different ways of converting

subclasses/superclasses into relational schemas.
Page 34

Database Lec 9 PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Database Lec 9 PDF

Caricato da

Copyright:

Formati disponibili

COSC 304

Introduction to Database Systems

Dr. Ramon Lawrence

ER Model to Relational Schemas

Conceptual database design produces a conceptual ER model.

Note that although it is possible to design using the relational

ER Model to Relational Schemas (2)

In general, these steps convert entities to relations and ER

Handling subclasses and superclasses in the EER model

After conversion is performed, normalization and optimization

1..1 0..* 0..* number {PK}

Employee (eno, ename, state, city, street, title, salary)

Project (pno, pname, budget)

Department (dno, dname)

For each weak entity W with identifying owners E1, E2, …, En

Employee (eno, ename, state, city, street, title, salary)

Project (pno, pname, budget)

Department (dno, dname)

Given a binary 1:1 relationship R between two entities Ei and Ej:

Department (dno, dname, mgreno, bonus)

Note: Renamed eno to mgreno for clarity.

Given a binary 1:N relationship R between two entities Ei and Ej:

Employee (eno, ename, state, city, street,

Project (pno, pname, budget, dno)

Project (pno, pname, budget, dno)

Department (dno, dname, mgreno, bonus)

Given a binary M:N relationship between entities Ei and Ej:

WorksOn (eno, pno, resp, hours)

Project (pno, pname, budget, dno)

Department (dno, dname, mgreno, bonus)

Given a multi-valued attribute A of entity Ei:

Project (pno, pname, budget, dno)

ProjectLocation (pno, location)

Project (pno, pname, budget, dno)

WorksOn (eno, pno, resp, hours)

Project (pno, pname, budget, dno)

ProjectLocation (pno, location)

Department (dno, dname, mgreno, bonus)

Given an n-ary relationship between entities E1, E2, …, En:

Part (pno, pname, desc) Project (jno, jname, budget)

Supplier (sno, sname, address)

EER to Relational Mapping

In general, we have several different approaches:

Given a superclass C and set of subclasses S1, S2, …, Sn:

Employee (eno, ename, state, city, street, title, salary, supereno)

ER to Relational Mapping Question

1) The M:N relationship mapping rule could be applied to 1:1

Order 0..* 0..* Part

The algorithm involves 7 steps for converting regular ER

In general, these steps convert entities to relations and ER

Be able to discuss the different ways of converting

Potrebbero piacerti anche