Checking and setting timestamps like last_leagues_update, etc occur in various places. This needs to be done in less (or one) place(s).
Given the multi-faceted nature of the application, we may need to settle on multiple places to check this as we define workflows for different use-cases. That is, if we want to be able to run huge queries involving refreshing lots of summoners at once, we may desire certain checks to be forgone (e.g. update X regardless of how old it is), but if an end-user wants to update their page, they should be subject to all the rules of a refresh that go along w/that.
Checking and setting timestamps like
last_leagues_update, etc occur in various places. This needs to be done in less (or one) place(s).Given the multi-faceted nature of the application, we may need to settle on multiple places to check this as we define workflows for different use-cases. That is, if we want to be able to run huge queries involving refreshing lots of summoners at once, we may desire certain checks to be forgone (e.g. update X regardless of how old it is), but if an end-user wants to update their page, they should be subject to all the rules of a refresh that go along w/that.