Oqallisissiat Howard Miller-imit allatat

Core developers-ip assinga Documentation writers-ip assinga Particularly helpful Moodlers-ip assinga Peer reviewers-ip assinga Plugin developers-ip assinga
No. It's a "custom" variation on the Gradebook. So, a load of fairly expensive aggregation calculations are done and I end up with a bunch of objects containing the results. What I don't want to have to do is to recalculate all (or some) of this when the user re-displays the grade table. BUT... I *do* need to invalidate it if something that would make a difference to the calculations changes. Obviously, I don't want to invalidate the data for every course, just this one. If that makes sense.
 
But I'm starting to think that storing intermediate results in the database may end up easier. Clearly, the table just has a 'courseid'. Easy.