Results 1 to 7 of 7

Thread: normalization!!

  1. #1
    Join Date
    Apr 2009
    Posts
    8

    Unanswered: normalization!!

    Am i right in saying that if a table has a field that has certain objects in it that repeat then another table should be made in which these objects do not repeat

    for example
    tblItem

    ItemCode Seller
    CED0001 Dell
    CED0002 Sony
    CED0003 Dell

    etc..


    Should another table be made, maybe called tblSeller where there is a list of the sellers? And if so is just one field enough in the table or should there be another?

  2. #2
    Join Date
    Feb 2004
    Location
    One Flump in One Place
    Posts
    14,912
    Yes...and no

    It is not so simple - if you have read normalisation you should be able to relate this question to a normal form.

    Based on what you have put in your question then absolutely not. However, if there is more to this then the answer might be "yes". Also, there is a further consideration not related to normalisation that might cause you to want to do what you propose.

    So, given that - let's step through this together.
    Quote Originally Posted by i8grand
    Am i right in saying that if a table has a field that has certain objects in it that repeat then another table should be made in which these objects do not repeat
    Why not tell us why you think this and also what normal form this relates to
    Testimonial:
    pootle flump
    ur codings are working excelent.

  3. #3
    Join Date
    Apr 2002
    Location
    Toronto, Canada
    Posts
    20,002
    Quote Originally Posted by i8grand
    Should another table be made, maybe called tblSeller where there is a list of the sellers? And if so is just one field enough in the table or should there be another?
    no, you do not have to do that, the only reason you'd want a sellers table is to enforce raltional integrity so that it will disallow inserting any rows into the tblItem tabletable which contain an invalid seller

    if you wanted to allow any sellers at all into the tblItem tabletable, then you wouldn't need the seller table

    and yes, one field is enough for a table

    rudy.ca | @rudydotca
    Buy my SitePoint book: Simply SQL

  4. #4
    Join Date
    Feb 2004
    Location
    One Flump in One Place
    Posts
    14,912
    That was a premature money shot for you Rudy
    Testimonial:
    pootle flump
    ur codings are working excelent.

  5. #5
    Join Date
    Apr 2002
    Location
    Toronto, Canada
    Posts
    20,002
    Quote Originally Posted by pootle flump
    That was a premature money shot for you Rudy
    sorry, i consider myself pretty au courant with britishisms, but "premature money shot" is completely undecipherable (and it ain't in wikipedia, neither)

    care to explain?

    ta

    rudy.ca | @rudydotca
    Buy my SitePoint book: Simply SQL

  6. #6
    Join Date
    Feb 2004
    Location
    One Flump in One Place
    Posts
    14,912
    The final climax. Normally you like to indulge in a little foreplay before you coax open the rose petals and expose their secrets.
    Testimonial:
    pootle flump
    ur codings are working excelent.

  7. #7
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    rofl poots!!
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

Posting Permissions

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