I’m not clear why it’s necessary to mechanically identify transitive m-2-m relationships among collections.
Moreover, it seems not to help understand relationships in practice.
Say, reviews and credit cards used for example in the lab.
user -< reviews
user -< credit cards
So, reviews >-< credit cards
Does it really suggest m-2-m to technically bridge them?
I think credit card -< reviews, 1-2-m makes sense.
However, review -< credit cards cannot establish the relationship
because one review is associated with one credit card that is used for the payment.
Guess same for stores - reviews.
store -< reviews can be true.
But likewise, review -< stores cannot be because a review is not common for all stores even for the same item.
Maybe, reviews need to have a
sold_at field to be more practical.
Can you help understand the value/meaning of transitive m-2-m relationships in data modeling?