That is more extensive than I had considered, but would cover some cases I had not thought of. I simply figured that teams would serve as what you named a club - effectively making them a grouping of players. Your suggestion would cover cases where there is the same team but different roster playing on different nights in the same season, and would serve as a better way to archive league standings (preserving team rosters).
I think I'll probably end up just updating the standings generator to take an optional season parameter, and filter out everything else in the set of scores. It looks like I can do this by adjusting the sql select in calculate_standings. I can't really think of a case where I'd have a league that has the scores from other leagues included in the standings. On Tue, Sep 8, 2009 at 1:50 PM, Dave O'Neill <[email protected]> wrote: > On Tue, Sep 08, 2009 at 01:29:24PM -0400, Greg Schmidt wrote: > > Have you created a new league with new teams? It sounds like you may be > > moving teams from the summer league to the fall league, which isn't the > > normal way. I believe that most leagues have very different sets of > teams > > from season to season, so creating new teams for each season makes the > most > > sense operationally. > > In Ottawa, we frequently have a mix of new teams and re-used teams from > a previous season. I'd say about half of OCUA's teams like to reuse > their team entry from a previous year, and half like to create a new > one. > > There's no nice way to deal with this in the application yet, but as > part of our pre-season prep, I manually remove the old schedule and > spirit entries from the database. For example, if you moved teams from > a league with the ID of 1 to a new league with a different ID, you can > run: > > DELETE FROM score_entry USING score_entry, schedule WHERE > score_entry.game_id = schedule.game_id AND schedule.league_id = 1; > DELETE FROM team_spirit_answers USING team_spirit_answers,schedule WHERE > team_spirit_answers.gid = schedule.game_id AND schedule.league_id = 1 > DELETE FROM gameslot USING gameslot, schedule WHERE gameslot.game_id = > schedule.game_id AND schedule.league_id = 1 > DELETE FROM schedule WHERE league_id = 1 > DELETE FROM league_gameslot_availability WHERE league_id = 1 > > to remove the games and results from the older league that are now > skewing your standings. Note that this will essentially render your > previous league useless, so be sure to back things up if you want to > preserve that information. > > At some point in the future (ie: whenever someone, probably me, has time > to implement it) I would like to fix this by introducing a new object to > the system. Instead of having a 'team' that has to move around from > league to league, you'd have two types of team-like object in the > system: > > 1) Club. This would exist across seasons and allow captains to tie > their teams from different seasons together into one group, manage > contacts, recruit for future seasons, etc. > > 2) Roster. This would be a subset of the players of a given club, > playing in a single season. > > Clubs would have multiple rosters, one for each season they're > participating in. > > Thoughts? > > Cheers, > Dave > _______________________________________________ > Leaguerunner mailing list > [email protected] > http://www.dmo.ca/cgi-bin/mailman/listinfo/leaguerunner >
_______________________________________________ Leaguerunner mailing list [email protected] http://www.dmo.ca/cgi-bin/mailman/listinfo/leaguerunner
