On Thu, Feb 26, 2009 at 6:26 PM, Jason Broyles <ja...@jasonism.org> wrote:
> > Thanks for the reply. I was talking about using memcache to cache the > view. If a search changes, will it get the cache or hit the database? > > On Feb 26, 6:11 pm, Alex Gaynor <alex.gay...@gmail.com> wrote: > > On Thu, Feb 26, 2009 at 6:08 PM, Jason Broyles <ja...@jasonism.org> > wrote: > > > > > I have a question about per view caching. Say I have a search form and > > > someone performs a query that returns all of the results, then those > > > results are cached. If they then did a new search with criteria in the > > > search, will it use the cache or hit the database again? Or if they > > > just sorted those results by an order_by, would it hit the database > > > again? > > > > It only doesn't hit the DB if you load something in from the cache. The > > buitin queryset caching just caches for the length of that object, it's > not > > any sort of global, cross request cache. > > > > Alex > > > > -- > > "I disapprove of what you say, but I will defend to the death your right > to > > say it." --Voltaire > > "The people's good is the highest law."--Cicero > > > Cache lookups occur by key, so if the key is found it will return the old queryset, it won't be invalidated because the result set *would* change unless you explicitly unset it. Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." --Voltaire "The people's good is the highest law."--Cicero --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
