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 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.
Regards, Constantin sandro dentella schrieb: > Hi all, > > I've being using django for a while now with great satisfaction, but > I've never needed to cope with cache system. > Now I'm hit by a problem that I believe is dependant on cache. I > have a form (newform), that in the .save() > method updates an object (it works!). Then reloading the page I > can't see the update. > > When I reload the page In the view I run a funcition that issues: > Model.objects.get(pk=1) and I get the /non/ > modified instance. If I go to the "manage.py shell" I get the / > modified/ instance. > > If I restart the devel server I still get the /unmodified/ > version.... > > I'm getting crazy... who's caching the result? > > I also managed to get a page with the same news in two different > places: one was cached and the other not. In that occasion I changed > the value via the admin interface. > > Any light to understand/solve it? > Thanks in advance > > 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 -~----------~----~----~----~------~----~------~--~---
