this is the answer, but the problem is partly solved.
On Thu, Apr 03, 2008 at 09:29:32AM -0700, Peter Rowell wrote:
>
> > Any light to understand/solve it?
>
> With any sort of suspected caching problem (and this certainly smells
> like one), Step 1 is always to disable caching, restart the server,
> and see if the problem magically goes away. If it does, you can put
> away the Xanax and start looking at where and how you are invoking the
> caching system.
>
> One thing you did not share with us was exactly *how* you are invoking
> caching. If you are using either the per-site caching middleware or
sorry. The fact is I neved /invoked/ caching:
1. no middleware
2. no decorator
3. I even added CACHE_BACKEND = 'dummy:///'
after reading this morning the docs on caching.
I went back to the view and realized that I was not usng a fresh instance
but the instance that I put into request.session. That instance was not
updated. Now I get it anew and it works.
For sure yesterday I has a similar problem that was not related to
session. Only restarting the server (devel or mod_wsgi) allowed me to
refresh news, but if I looked at the detail I always got the write one from
the db. What was failing was a objects.all().order_by('-date')[:3].
sandro
*:-)
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
