title: Python Django cache vs store in model field? Which is more efficient?
body: <p>My view displays a table of data (specific to a customer who may have many users) and this table takes up a lot of computational resource to populate. A customers data changes 4/5 times a week, usually on the same day.</p>
  
  <p>Caching is an obvious solution to this but I was wondering if <a href="https://docs.djangoproject.com/en/1.11/topics/cache/" rel="nofollow noreferrer">Django's cache framework</a> is significantly more efficient than creating a Textfield at the customer level and storing the data there instead?</p>
  
  <p>I feel it's easier to implement (and clear the Textfield when the data changes) but what are the drawbacks and is there anything else I need to look out for? (problems if the dataset gets too big? additional fields in the model etc etc???)</p>
  
  <p>Any help would be much appreciated! </p>