In a view. I know that the cache is updated automatically, but the problem is that the cache is generating numbers that does not exists, and when the page is consulting the cache to get the values, it show a value that does not exists in really if you look into the database. It's really strange.
The number 487.000 for example, that would stay the same value for all the time is changing with a certain frequency when django consult it's cache in /var/tmp/djangocache and the value showed is 287.000. The cache is generating strange values that I don't know where they come from. On 10 ago, 14:25, Aljoša Mohorović <aljosa.mohoro...@gmail.com> wrote: > On Tue, Aug 10, 2010 at 7:17 PM, Felipe <felipecat...@gmail.com> wrote: > > So, > > > I'm using a filesystem caching and I'm using cache.get and cache.set > > to set and get the cache. > > > But sometimes django shows a different value of the stored value in > > the database. > > cache is not updated automatically, if value in database has changed > you need to update cache. > where are you caching (cache.set) this value, in a view or after > Model.save() is called? > post part of code where you are using cache.get/set. > > Aljosa -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
