locked
Classification of Tables/Relationships RRS feed

  • General discussion

  • What are the common classifications of table types.  

    for example the classic orders and details would be a parent/child, and a employee table would be a lookup table.

    (i think i get a little confused because foreign keys are termed parent child even though they are not truly a parent child relationship)

    am i using the right terminology for these relationships and what types are there that i am missing.  i have tried to google this but not had luck.

    thanks.  sorry if i did not explain what i am looking for really well.


    Coding 4 God!
    Friday, November 4, 2011 8:09 PM

All replies

  • According to Celko, parent and child are not correct terms (although widely used and I use it often myself). Check his answer in this thread

    http://social.msdn.microsoft.com/Forums/en-US/transactsql/thread/379f1ea1-bfff-453f-b297-ff1b9d646a8d/


    For every expert, there is an equal and opposite expert. - Becker's Law


    My blog
    Friday, November 4, 2011 8:37 PM
    Answerer
  • so what then would you call the relationship?  i think i missed the answer to that in your link.
    Coding 4 God!
    Friday, November 4, 2011 8:48 PM
  • I actually googled a bit more and found another thread (wow, I forgot about it, but it was quite interesting discussion)

    http://social.msdn.microsoft.com/Forums/en-US/transactsql/thread/c4d4f72c-35a7-43f9-8dbc-5517a14de5f2/

    So, Celko uses “referenced” and “referencing” tables. 


    For every expert, there is an equal and opposite expert. - Becker's Law


    My blog
    Friday, November 4, 2011 9:02 PM
    Answerer
  • naomi,

     

    thanks for researching it for me.  referenced and referencing certainly makes more sense than parent table.  however what i was looking for was more what abstract classifications are there for relations no matter how the tables relate the relationship object its self will involve a referencing and reference table but does not indicate the type of relationship ie lookup table associative ect.  so far if i google types of relationships i get 1 to 1 many to 1 ect.  but cant find anything else.


    Coding 4 God!
    Friday, November 4, 2011 9:21 PM
  • >classic orders and details would be a parent/child

    Sort of. It is a parent/child relationship, the TABLEs themselves, however, are "master" and "detail". Going back the hierarchical databases, the terms "master" and "child" are common. Though, in a case of orders, sometimes the specific term "line item" is used.

    Personally, i use "object" instead of "master". Everyone understands, and that should be all that matters.

    >and a employee table would be a lookup table.

    Lookup TABLEs are TABLEs whose sole purpose is to hold values, generally identified by begin just the Name and Description (and commonly a redundant surrogate Id as the PK). Employee_Type is a lookup, Language is a lookup, Employee is an Object or "main" TABLE.

     

     

     

     

    Monday, November 7, 2011 1:28 PM
    Answerer