On Thu, Apr 03, 2008 at 06:51:49PM +0200, Constantin Christmann wrote: > > Hi Sandro, > > this is indeed a caching issue. But I guess this is more of a feature > that a bug, because with caching enabled you keep an old page some time
it's a feature if you can control it... > until it's expired. > Adjacent request get this old page stored in the cache which decreases > server and database load. > If you bypass this cache (via shell or admin interface) you see the > current database status. As I told I had 1 page with the same news represented in a "detail" page, and in a little box. The 2 representation did not match. I was looking for a way to tell the orm I want a fresh copy from the db ie, I want to invalidate the cache and start from the beginning. more. I'd like to understand why one of the 2 query used the cache and the other didn't. 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 -~----------~----~----~----~------~----~------~--~---
