Home/ Questions/Q 4015986
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T09:41:07+00:00

I’m trying to make a simple tournament system, and now I’ve come to another

  • 0

I’m trying to make a simple tournament system, and now I’ve come to another wall…
I have a Table named Teams – Each Team can participate in multiple matches.

I’ve thought about having a table named Matches which have 4 columns:

  • ID => Identifier
  • Team1ID => Reference to ID in Teams
  • Team2ID => Reference to ID in Teams
  • WinnerID => Same value as either Team1ID or Team2ID

WinnerID will then have a sql trigger that checks whether its the same value as Team1ID or Team2ID… If not it will rollback the transaction.

This approach seemed perfect in the start, until I realized that it broke several “best practice” rules, including the “repository per aggregate root” because it would require me to do:

Team myTeam1 = ... Get team1 ...
Team myTeam2 = ... Get team2 ...

Match myMatch = new Match { Team1 = myteam1, Team2 = myteam2; }

which is wrong since the Match entity is defined as a “child entity” for the Team entity, and should only be added through the Team entity.

Any suggestions about how to design my database properly to fit my needs?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    As far as the trigger, I would just use some constraints.

    (Team1ID <> Team2ID)
AND
(WinnerID IS NULL OR Team1ID = WinnerID OR Team2ID = WinnerID)

    probably all in one constraint.

    As far as the domain model, I would not have thought you add a match through a team, but perhaps through a tournament instance: Match = Tournament.NewMatch(Team1, Team2) ;

    Conceivably, there would be higher order tournament rules, like rounds, eliminations, etc.

    Since it sounds like your Teams know their Cup, then to create a Team or retrieve it from the database, it would go through the Cup: Cup.NewTeam(TeamName) or Cup.LoadTeam(TeamID). It would still make sense then for Cup.NewMatch, since you certainly wouldn’t want to have a match between teams in different Cups.

    • 0