Add one more table to database scheme to group subdivisions by division.
This way, a division can have a shared name key between all its subdivisions,
e.g. division "Silver" has subdivisions "I", "II", and "III", which will then be displayed as "Silver I" (etc.) in the client.
This also simplifies graphing of score over time where one would like to group by division.
These changes only touch the league rating service where it is concerned with loading division data for each league.
Subdivisions are still represented as a flat list of independent divisions for rating purposes, so nothing changes and the rater is not aware of division boundaries.
Closes #5
[Merge is currently pointing to issue/#004-handle-new-players so that the diffs make more sense, should merge the other PR first and then point this one at develop.]
Add one more table to database scheme to group subdivisions by division. This way, a division can have a shared name key between all its subdivisions, e.g. division "Silver" has subdivisions "I", "II", and "III", which will then be displayed as "Silver I" (etc.) in the client. This also simplifies graphing of score over time where one would like to group by division.
These changes only touch the league rating service where it is concerned with loading division data for each league. Subdivisions are still represented as a flat list of independent divisions for rating purposes, so nothing changes and the rater is not aware of division boundaries.
Closes #5
[Merge is currently pointing to
issue/#004-handle-new-playersso that the diffs make more sense, should merge the other PR first and then point this one atdevelop.]