database - Django, is manual caching a bad idea? -

some of reports taking far long. i've implemented "cache" fields solve problem. example student's gpa involved calculation. i've add non normalized gpa field student. on each grade update, gpa recalculated , can assumed gpa field current.

i know there number of caching mechanisms in django. correct wouldn't able this?

you work around problem using django's cache framework, you'd go things differently. can cache want it, it's not designed save results on object. if want avoid calculating gpa , still able access off each model instance way going simple , best way it.