Results 1 to 2 of 2
  1. #1
    Join Date
    Sep 2015



    Iīm just reading a course in databases and I got my examresult back yesterday and I didnīt get through.
    The big problem is that what I read about normalizations is that you should avoid redundance.
    In this case, where we get the answer together with the exam i just donīt get the logic, because there would be A LOT of redundance with date, time and seat.
    Isnīt the rule "avoid redundance" the first rule of normalization or am I thinking all wrong?

    Click image for larger version. 

Name:	Question.png 
Views:	10 
Size:	56.6 KB 
ID:	16548Click image for larger version. 

Name:	Answers.png 
Views:	8 
Size:	19.5 KB 
ID:	16549


  2. #2
    Join Date
    Feb 2012
    Normalization isn't concerned with redundant values, it's meant to reduce redundant associations between values. Values that are recorded multiple times are perfectly normal if they're involved in multiple relationships. However, when a functional or multivalued dependency (one-to-one or one-to-many relationship) is recorded more than once, there's a risk that only some of the rows could be updated, causing inconsistent data.

    In your example, see in the 1NF table how filmId -> filmName is recorded multiple times, so too personNr -> name, telephone, as well as (date, time, seatNr) -> personNr and (date, time) -> filmId. When normalizing, we look for patterns of duplication between related columns, not just in one column.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts