New answers tagged application-design
If you want a history of the all the players that have passed in that team the approach: Team 1:N Contracts N:1 Players is fine. Otherwise if you just want to know the players that are currently in the team and contract is not a needed information for you, the approach: Team 1:N Player will also work
I'll try to explain why they merge all relationships into one table. Whether a users follows, likes or comments a photo all these activities are somewhat similar they involve a user and photo. Note that the comment also requires some text. So instead of having 3 tables like your data model they went with one. I don't like that approach though because it ...
Top 50 recent answers are included