On Thu, Aug 27, 2009 at 5:34 PM, Sam Tregar<s...@tregar.com> wrote: > Hey all. So, I figured out how to run my QuerySet through MySQLdb's > SSCursor! Woo! > > Bad news: it's still using a ton of memory. As far as I can tell it's being > used by QuerySet's internal _result_cache which is holding all the rows > retrieved by the query. Is there any way to turn this cache off? Looking > at the code leads me to think no, but I thought I'd ask. > > -sam > > > > >
Instead of iterating over the QuerySet itself, use QuerySet.iterator(), this will avoid populating the result 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 "Code can always be simpler than you think, but never as simple as you want" -- Me --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
