We are reviewing the GameBorrow table. The GameID and GamerID attributes are foreign keys to the Game
Fantastic news! We've Found the answer you've been seeking!
Question:
We are reviewing the GameBorrow table. The GameID and GamerID attributes are foreign keys to the Game and Gamer tables respectively, first and last are the Gamer's first and last name, startDate is when the loan is taken out and expiry is when the loan expires. We have revised our assumption and now assign a GameID to every copy of a Game. For example, we have 3 copies of Mario Kart. Their GameIDs are 6631, 6632 and 6633 respectively. The table structure is as below:
GameBorrow | |||||
GameID | GamerId | Gamer_FirstName | Gamer_LastName | Start | Expiry |
6621 | 1200 | Anna | Smith | 01/01/2001 | 03/01/2001 |
5622 | 896 | Sam | Goldview | 05/02/2001 | 07/02/2001 |
6589 | 2852 | Garry | Blair | 11/1/2001 | 13/1/2001 |
We have to test whether this table is in 3NF under the new assumptions. Which of the answers is true:
- The GameBorrow table is in 2NF but not in 3NF, because there is a transitive dependency between the Gamer_FirstName and Gamer_FirstName attributes and the composite key of GameID + Start, because the composite key defines GamerID and GamerID defines Gamer_FirstName and Gamer_LastName
- The GameBorrow table is in 1NF but not in 2NF, because the Gamer_FirstName and Gamer_LastName attributes are only partially dependent on the composite key of GameID + GamerID + Start.
- The GameBorrow table is in 1NF but not in 2NF, because the GamerID attribute is only partially dependent on the composite key of GameID + Gamer_FirstName + Gamer_LastName + Start.
- The GameBorrow table is in 2NF but not in 3NF, because there is a transitive dependency between the Gamer_FirstName and Gamer_LastName attributes and the GameID key which is the most suitable key for this table. GameID defines GamerID and GamerID defines Gamer_FirstName and Gamer_LastName.
Please specify the number and explain the correct answer
Posted Date: