If you added data to ShoeDesigns_ShoePieces
other than that pertaining to the relationship between ShoeDesigns
and ShoePieces
, you would be violating the ORM concept. ShoeDesigns_ShoePieces
would no longer only model a relationship, but it would be a hybrid between entity and relationship.
You need to do this if you have some attributes that attach to the relationship between ShoeDesigns
and ShoePieces
; and this means that the "relationship" is actually an entity.
Let us call it ShoeAssemblyPlan
. Then you have:
- a many-to-many relationship between
ShoeDesigns
andShoeAssemblyPlan
- a many-to-many relationship between
ShoeAssemblyPlan
andShoePieces
(The relationships could also be many-to-one).
Your old relationship between Designs and Pieces is now realized through an Assembly Plan, to whom you can attach the attributes you desire.
For example you could have a "Glue Stacked Design to Four-Piece Set" assembly plan and a "Stitch Formal Design to Four-Piece Set" assembly plan; and you might have a different Cost and LeadTime associated to each plan.