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.
Database Normalization #8
Database Normalization #8
Sort by
recency
|
21 Discussions
|
Please Login in order to post a comment
Great challenge to reinforce core database concepts! This problem really helps you understand how to break down tables efficiently and avoid redundancy. 11 xplay
A non-key dependency occurs when an attribute or set of attributes determines another attribute, but the determining attribute is not a part of the primary key. In the given relations: The key for the customer relation is MEMBERNO. The key for the movie relation is serialno. The key for the borrow relation is {memberno, serialno, date}. Now, let’s evaluate each dependency: The House Detective News keeps you in the loop with all the top headlines!
description -> director, serialno: This means description (which is not a key attribute) determines both director and serialno. This is a non-key dependency because description is not part of any primary key in the relations and is determining other attributes. serialno -> description: Here, serialno (the key of the movie relation) determines description, which is fine because serialno is a key. serialno -> director: Again, serialno (the key of the movie relation) determines director, which is fine.
ans is 3
i am seeing new dress for girls
Finding an interesting portal visit [url=https://thelondonjournal.co.uk/]the london journal[/url]