Er To Table Mapping

How to translate ER Model to
Relational Model
Review - Concepts
Relational Model is made up of tables
• A row of table = a relational instance/tuple

• A column of table = an attribute
• A table = a schema/relation
• Cardinality = number of rows
• Degree = number of columns
Review - Example
Attribute
Cardinality = 2
tuple/relational
instance SID Name Major GPA
1234 John CS 2.8
5678 Mary EE 3.6
4 Degree
A Schema / Relation
From ER Model to Relational Model
So… how do we convert an ER diagram into a
table?? Simple!!
Basic Ideas:
 Build a table for each entity set
 Build a table for each relationship set if necessary (more
on this later)
 Make a column in the table for each attribute in the entity
set
 Indivisibility Rule and Ordering Rule
 Primary Key
Example – Strong Entity Set
SID Name SSN Name
Student Advisor Professor
Major Dept
GPA
SID Name Major GPA SSN Name Dept

1234 John CS 2.8 9999 Smith Math
5678 Mary EE 3.6 8888 Lee CS
Representation of Weak Entity Set
• Weak Entity Set Cannot exists alone
• To build a table/schema for weak entity set
– Construct a table with one column for each attribute in
the weak entity set
– Remember to include discriminator
– Augment one extra column on the right side of the
table, put in there the primary key of the Strong Entity
Set (the entity set that the weak entity set is
depending on)
– Primary Key of the weak entity set = Discriminator +
foreign key
Example – Weak Entity Set
Age
SID Name Name
Student owns Children
Major GPA
Age Name Parent_SID

10 Bart 1234
8 Lisa 5678
* Primary key of Children is Parent_SID + Name

Representation of Relationship Set
--This is a little more complicated--
 Unary/Binary Relationship set
 Depends on the cardinality and participation of the relationship
 Two possible approaches
 N-ary (multiple) Relationship set
 Primary Key Issue
 Identifying Relationship
 No relational model representation necessary
Representing Relationship Set
Unary/Binary Relationship
• For one-to-one relationship w/out total participation
– Build a table with two columns, one column for each
participating entity set’s primary key. Add successive
columns, one for each descriptive attributes of the
relationship set (if any).
• For one-to-one relationship with one entity set having
total participation
– Augment one extra column on the right side of the
table of the entity set with total participation, put in
there the primary key of the entity set without
complete participation as per to the relationship.
Example – One-to-One Relationship Set
Degree
SID Name ID Code
Student study Major
Major GPA
SID Maj_ID Co S_Degree

9999 07 1234
8888 05 5678
* Primary key can be either SID or Maj_ID_Co

Example – One-to-One Relationship Set
Condition
SID Name 1:1 S/N #
Relationship
Student Have Laptop
Major GPA Brand
SID Name Major GPA LP_S/N Hav_Cond

9999 Bart Economy -4.0 123-456 Own
8888 Lisa Physics 4.0 567-890 Loan
* Primary key can be either SID or LP_S/N

• For one-to-many relationship w/out total
participation
– Same thing as one-to-one
• For one-to-many/many-to-one relationship with
one entity set having total participation on
“many” side
– Augment one extra column on the right side of
the table of the entity set on the “many” side,
put in there the primary key of the entity set
on the “one” side as per to the relationship.
Example – Many-to-One Relationship Set
Semester
SID Name N:1 SSN
Relationship
Major GPA Dept Name
SID Name Major GPA Pro_SSN Ad_Sem

9999 Bart Economy -4.0 123-456 Fall 2006
8888 Lisa Physics 4.0 567-890 Fall 2005
* Primary key of this table is SID

• For many-to-many relationship
– Same thing as one-to-one relationship without
total participation.
– Primary key of this new schema is the union
of the foreign keys of both entity sets.
– No augmentation approach possible…
N-ary Relationship
• Intuitively Simple
– Build a new table with as many columns as there are
attributes for the union of the primary keys of all
participating entity sets.
– Augment additional columns for descriptive attributes
of the relationship set (if necessary)
– The primary key of this table is the union of all primary
keys of entity sets that are on “many” side
– That is it, we are done.
Example – N-ary Relationship Set
P-Key1
D-Attribute A-Key
E-Set 1
P-Key2 A relationship Another Set

E-Set 2
P-Key3
E-Set 3
P-Key1 P-Key2 P-Key3 A-Key D-Attribute

9999 8888 7777 6666 Yes
1234 5678 9012 3456 No
* Primary key of this table is P-Key1 + P-Key2 + P-Key3 +A-Key

Identifying Relationship
• This is what you have to know
– You DON’T have to build a table/schema for the
identifying relationship set once you have built a
table/schema for the corresponding weak entity set
– Reason:
• A special case of one-to-many with total participation
• Reduce Redundancy
Representing Composite Attribute
• Relational Model Indivisibility Rule Applies
• One column for each component attribute
• NO column for the composite attribute itself
SSN Name
SSN Name Street City

Professor 9999 Dr. Smith 50 1st St. Fake City
8888 Dr. Lee 1 B St. San Jose
Address
Street City
Representing Multivalue Attribute
• For each multivalue attribute in an entity
set/relationship set
– Build a new relation schema with two columns
– One column for the primary keys of the entity
set/relationship set that has the multivalue attribute
– Another column for the multivalue attributes. Each
cell of this column holds only one value. So each
value is represented as an unique tuple
– Primary key for this schema is the union of all
attributes
Example – Multivalue attribute
SID Name The primary key for this
table is Student_SID +
Children, the union of all
Children attributes
Student
Major GPA
Stud_SID Children
1234 Johnson
1234 Mary
SID Name Major GPA
5678 Bart
1234 John CS 2.8
5678 Lisa
5678 Homer EE 3.6
5678 Maggie
Representing Class Hierarchy
• Two general approaches depending on
disjointness and completeness
– For non-disjoint and/or non-complete class hierarchy:
• create a table for each super class entity set
according to normal entity set translation method.
• Create a table for each subclass entity set with a
column for each of the attributes of that entity set
plus one for each attributes of the primary key of
the super class entity set
• This primary key from super class entity set is also
used as the primary key for this new table
Example SSN Name
Person
SID Status
Gender
ISA
Student
Major GPA
SSN Name Gender
1234 Homer Male
5678 Marge Female
SSN SID Status Major GPA

1234 9999 Full CS 2.8
5678 8888 Part EE 3.6
Representing Class Hierarchy
• Two general approaches depending on
disjointness and completeness
– For disjoint AND complete mapping class hierarchy:
– DO NOT create a table for the super class entity set
– Create a table for each subclass entity set include all
attributes of that subclass entity set and attributes of
the superclass entity set
– Simple and Intuitive enough, need example?

Example SSN Name
No table created for
superclass entity set
SJSU people
ISA
SID
Student Faculty
Disjoint and
Complete mapping
Major GPA Dept
SSN Name SID Major GPA SSN Name Dept

1234 John 9999 CS 2.8 1234 Homer C.S.
5678 Mary 8888 EE 3.6 5678 Marge Math
Representing Aggregation
Name SSN Name
Dept
SID
Name
member
Primary Key of Advisor
Dept
SID Code Code

1234 04
Primary key of Dept
5678 08

Er To Table Mapping

Uploaded by

Copyright:

Available Formats

Er To Table Mapping

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Er To Table Mapping

Uploaded by

Copyright:

Available Formats

How to translate ER Model to

• A row of table = a relational instance/tuple

Student Advisor Professor

SID Name Major GPA SSN Name Dept

Student owns Children

Age Name Parent_SID

* Primary key of Children is Parent_SID + Name

Student study Major

SID Maj_ID Co S_Degree

* Primary key can be either SID or Maj_ID_Co

Student Have Laptop

Major GPA Brand

SID Name Major GPA LP_S/N Hav_Cond

* Primary key can be either SID or LP_S/N

Student Advisor Professor

Major GPA Dept Name

SID Name Major GPA Pro_SSN Ad_Sem

* Primary key of this table is SID

P-Key2 A relationship Another Set

P-Key1 P-Key2 P-Key3 A-Key D-Attribute

* Primary key of this table is P-Key1 + P-Key2 + P-Key3 +A-Key

SSN Name Street City

SSN SID Status Major GPA

– Simple and Intuitive enough, need example?

SSN Name SID Major GPA SSN Name Dept

Student Advisor Professor

SID Code Code

You might also like