Make sure players' game_count is saved correctly before they are placed. This requires saving LeagueScores with division_id and score set to None for players who haven't been placed yet.
Also needed to adjust the database schema to the new league_rater conventions:
In league_season_division min_rating, max_rating, highest_score may not be null, so that comparisons in the rater don't fail.
In league_season_score division and score may now be null to save score before placement.
I don't like that we currently have to enforce some data consistency on write, since league_season_score carries both a season_id and a division_id, which has its own season_id attached. It would be better not to duplicate this information.
The plain season_id is needed to be able to store scores without division before placement.
Make sure players' game_count is saved correctly before they are placed. This requires saving
LeagueScoreswithdivision_idandscoreset toNonefor players who haven't been placed yet.Also needed to adjust the database schema to the new league_rater conventions: In
league_season_divisionmin_rating, max_rating, highest_score may not be null, so that comparisons in the rater don't fail. Inleague_season_scoredivision and score may now be null to save score before placement.I don't like that we currently have to enforce some data consistency on write, since
league_season_scorecarries both aseason_idand adivision_id, which has its ownseason_idattached. It would be better not to duplicate this information. The plainseason_idis needed to be able to store scores without division before placement.Closes #4