On Thu, Aug 27, 2009 at 8:18 PM, Alex Gaynor <alex.gay...@gmail.com> wrote:
> > On Thu, Aug 27, 2009 at 5:56 PM, Sam Tregar<s...@tregar.com> wrote: > > On Thu, Aug 27, 2009 at 5:47 PM, Alex Gaynor <alex.gay...@gmail.com> > wrote: > >> > >> Instead of iterating over the QuerySet itself, use > >> QuerySet.iterator(), this will avoid populating the result cache. > > > > Thanks, works great! This would make a good addition to the manual > section > > that describes how the QuerySet cache system works. Maybe I'll see about > a > > patch. > > > > -sam > > > > > > > > > > > Note that the iterator() method is documented in the QuerySet > documentation: > http://docs.djangoproject.com/en/dev/ref/models/querysets/#iterator Good point. If the description had used the word "cache" I might have even found it when I was searching for a workaround. -sam --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
