















Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community for help and clear up your study doubts
Discover the best universities in your country according to Docsity users
Free resources
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
DB and Math Relations, Properties of DB, Order of columns, Mathematical relation, Degree and Cardinality, Relations Keys, Integrity Constraints are the main points of this lecture.
Typology: Slides
1 / 23
This page cannot be seen from the preview
Don't miss anything!
Properties of DB relations are similar to those of Mathematical relations, except
The order of columns in Mathematical relation does matter
The concept of key and all different types of keys are applicable to the Relations
Foreign Key: An attribute of a table B that is primary key in another table A
Consider table EMP and DEPT
EMP (empId, empName, qual, depId)
DEPT (depId, depName, numEmp)
Constraints help to maintain the correctness, validity or integrity of the database Like null constrains, default value, domain constraint
Logical DB design is obtained from conceptual DB design
Generally involves transforming E-R data model to relational data model
We have studied both DMs, now how to perform transformation
Straightforward rules exist
Can be performed manually as well as automatically
Evaluate even if you use some tool, since multiple options exist
Since tables can contain only
atomic values composite attributes need to be represented as a separate relation
Quality becomes a limitation
An ET with a multi-valued
attribute is transformed into two relations
One contains the entity type and
second the muli-valued attribute
The PK of the second relation is the PK of first relation and the attribute value itself
Values are accessed through reference of the PK, that also serves as FK
Identifier dependency: relation
for weak entity type is created and the PK of the strong ET is used as a whole or part of the relation against weak ET