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

    Quick question regarding data redundancy

    I'm trying to create a DVD database (more on that later-in another post). I've run into a situation where some data is sometimes, but not always duplicated in a table.

    This is just part of one table, but illustrates what I'm talking about.

    Click image for larger version. 

Name:	Capture.PNG 
Views:	2 
Size:	6.3 KB 
ID:	16186

    My question is: Assuming that the duplication is coincidental ("Buffy - Season 3" just happens to be in a case called "Buffy - Season 3"). Assuming also that TitleName and CaseName are independent of each other (if I change one, I do not want the other to be effected).

    Can I avoid adding a separate Case table? I really would prefer not to if I don't have to.
    Attached Thumbnails Attached Thumbnails Capture.PNG  

  2. #2
    Join Date
    Nov 2004
    out on a limb
    Why would you need a separate case table?
    the casename is an attribute of the film/tv programme mot a separate entity in itsown right. It could be if you could argue that the same title may have different case names.

    If the title name and case name can be different then they are different attributes, requiring different columns to store the data, even if they sometimes have the same actual data.
    as to how you handle it, well thats up to you.
    you could store the same data in both columns.
    you could store nothing in the case name when its the same as the title name.
    I'd rather be riding on the Tiger 800 or the Norton

Posting Permissions

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