To avoid redundancies in the `Order` entity, attributes should be normalized to ensure that related data is stored in separate tables and redundancies are minimized. Typically, you would normalize by separating entities into distinct tables where data is repeated or has multiple occurrences.
In this context, you need to consider attributes that would cause redundancy if included in the `Order` entity:
1. `OrderDate`: This should be kept in the `Order` table as it pertains to the order itself.
2. `ItemId`: This identifies the item and should be a foreign key to a separate `Item` table to avoid redundancy.
3. `ItemName`: This should be in the `Item` table, not in the `Order` table, to avoid redundancy since the item name is associated with `ItemId`.
4. `Quantity` and `ItemPrice`: These are related to the specific item ordered and are specific to the `OrderItem` relationship.
So, the attributes that should be separated to avoid redundancies are:
B. ItemName - ItemPrice
`ItemName` should be moved to the `Item` table, and `ItemPrice` should be managed in the `Item` table or in an `OrderItem` table to avoid duplicating item details for each order.
upvoted 1 times
...
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Rabbitsfoot
5 months, 2 weeks agoRabbitsfoot
5 months, 2 weeks ago