I have started writing a cup tree and it works now.
Now I want to ask a good database structure for a tournament.
I thought this way:
table participant -------------- ID of the player ID table table ---- ------- Player ID Round Table Cup Match ID of Cup ID ----------------- ID ID Cup ID Player A Number: BB Number Result Number Number B Is this a good design?
Workflow:
The first round: All the particles joined. Matches are produced for round one.
The player enters the result (he has won). PlayerB acknowledges the Bayeux match is accepted, entered into the round. Player A is now in the next round.
The next matches are created after entering the next match
Why not store the round number in the attendee number table? I (A) see no reason to store this attribute in a separate table or (b) accumulating an entry for each round of entering each player. Maximum per-goal per player should be sufficient.
In addition, on your application, you can add round number to a match. I know that this is useless, because you can get it by looking at the number of times of Aaron, but when there are so many requests for this information, then the additional question should be saved!
Comments
Post a Comment