So far I don't have this issue at all with 1.4, which makes sense as it started exactly at the 1.5 upgrade time for me.
On Monday, April 1, 2013 7:40:08 AM UTC-6, [email protected] wrote: > > So I have some stats reports that I run that it almost seems as if each > thread has its own queryset cached. Each time I refresh they change. I'm > going to revert back to 1.4 due to this bug. I wish I could come up with a > simple example, to demonstrate this, the problem is that the underlying > database needs to change between the time each thread serves a request. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
