Luke Plant wrote: > On Saturday 11 February 2006 19:07, Robert Wittams wrote: > > >>So I would suggest: >> >>Article.objects: >> >> is a query set that supports all the normal operations, but is >>uncached >> >>Article.objects.cached(): >> >> is a query set that is cached. Otherwise the same as Article.objects > > > In this case, would Article.objects.filter(foo=bar) also automatically > turn caching on, or would you have to do > Article.objects.cached().filter(foo=bar) > ? > > Luke
I was imagining that any call that created a new query set (ie modified some search parameter) would turn caching on. Of course, this wouldn't cache across calls that happened to end up with the same query. ( That would necessitate hanging the cache off a context variable as I talked about before). The only real 'trouble' situation is the manager that is stored in the class, I think.
