We use cookies to ensure you have the best browsing experience on our website. Please read our cookie policy for more information about how we use cookies.
When we merge all three tables into one universal relation
𝑅(name, addr, memberno, description, director, serialno, date)
R(name, addr, memberno, description, director, serialno, date)
and apply the normal-form rules:
It clearly has atomic columns → 1NF holds
There are no partial dependencies on a composite key → 2NF holds
However, it exhibits a transitive dependency
(serialno, date) → memberno →(name, addr)
(serialno,date)→memberno→(name,addr)
where name and addr depend indirectly on serialno and date, violating 3NF’s “no non-key → non-key” rule
.
Since it fails 3NF, it cannot be in BCNF.
Thus, the highest normal form satisfied is 2NF.
Cookie support is required to access HackerRank
Seems like cookies are disabled on this browser, please enable them to open this website
Database Normalization #6
You are viewing a single comment's thread. Return to all comments →
When we merge all three tables into one universal relation
𝑅(name, addr, memberno, description, director, serialno, date) R(name, addr, memberno, description, director, serialno, date) and apply the normal-form rules:
It clearly has atomic columns → 1NF holds
There are no partial dependencies on a composite key → 2NF holds
However, it exhibits a transitive dependency
(serialno, date) → memberno →(name, addr) (serialno,date)→memberno→(name,addr) where name and addr depend indirectly on serialno and date, violating 3NF’s “no non-key → non-key” rule
.
Since it fails 3NF, it cannot be in BCNF.
Thus, the highest normal form satisfied is 2NF.