Alright, I think I answered my own question. It seems the current
RequestContext is a little messed up and not only requests cache to be
remade, but also crashes runserver upon more than 1 request.
On Nov 30, 7:26 pm, Chris G <[EMAIL PROTECTED]> wrote:
> I have a large query that is ran and takes about 50 seconds to
> completely and is pretty resource intensive. So what I have done is
> cached it into a key via cache.set('my_query_results', results, 300)
>
> The problem is that I also use pagination which results from this
> query. So when navigating to ?page=2~ it should in theory just re-use
> the cache and output page 2's data. But it doesn't. What it does is re-
> run and re-cache the entire query again. I'm guessing that this is due
> to the 'request' (MyView(request) is changing (?page=2).
>
> Is it possible to override this? Or am I just doing something this
> whole thing wrong?
>
> Thanks
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
