Is there a general term for a pairing of tables where one has header information and the other has detail lines?
For example, a pair of tables describing sales orders, or a pair storing bill of materials data.
views:
63answers:
4
+4
A:
One-To-Many describes the "numbers".
But one could prefer Parent-Child in some contexts, typically when the Child always has a Parent...
KLE
2009-10-09 16:03:34
+1
A:
Remember that it is a good practice to use consistent naming conventions in your database for these types of tables. Doesn't really matter what names, consistency is really the key. The goal is to have a general idea of what the table holds based on the name. Some I've seen:
(Assume the table holds Products)
Product -- ProductDetail
ProductHeader -- ProductDetail
Product -- ProductLines
For me, Parent-Child names imply a hierarchical relationship, which is a whole 'nother ball of wax.
Audrey
2009-10-13 18:39:39
I think Master/Detail is the best answer, since it's at the correct level of abstraction. It's true that there's a parent/child hierarchy, since each detail/line has exactly one parent, but that's a matter of implementation.
Steven Sudit
2009-10-17 17:30:01