Académique Documents
Professionnel Documents
Culture Documents
Mapping
Logical DB Design: ER to Relational
name
ssn lot
35
Employees
CREATE TABLE
Employees
(ssn CHAR(11),
name CHAR(20),
lot INTEGER,
PRIMARY KEY
Relationship Sets to Tables
CREATE TABLE Works_In(
In translating a many-to- ssn CHAR(1),
many relationship set to a did INTEGER,
relation, attributes of the since DATE,
relation must include:
PRIMARY KEY (ssn, did),
Keys for each
FOREIGN KEY (ssn)
participating entity set
(as foreign keys). REFERENCES Employees,
This set of attributes FOREIGN KEY (did)
forms a superkey for REFERENCES Departments
the relation.
All descriptive
attributes.
3/3/93
2/2/92
Review: Key Constraints
since
Each dept has at name dname
most one manager, ssn lot did budget
according to the
key constraint on
Manages. Employees Manages Departments
Translation to
relational model?
Works_In
since
Participation Constraints in SQL
We can capture participation constraints
involving one entity set in a binary relationship,
but little else (without resorting to CHECK
constraints).
CREATE TABLE Dept_Mgr(
did INTEGER,
dname CHAR(20),
budget REAL,
ssn CHAR(11) NOT NULL,
since DATE,
PRIMARY KEY (did),
FOREIGN KEY (ssn) REFERENCES Employees,
ON DELETE NO ACTION)
Review: Weak Entities
A weak entity can be identified uniquely only by
considering the primary key of another (owner)
entity.
Owner entity set and weak entity set must
participate in a one-to-many relationship set (1
owner, many weak entities).
Weak entity set must have total participation in this
identifying
namerelationship set.
cost pname age
ssn lot
hourly_wages hours_worked
ISA
As in C++, or other PLs, contractid