#31582: Django template backend allocates model cache even iterator() is used
     Reporter:  Sümer Cip        |                    Owner:  nobody
         Type:  Bug              |                   Status:  closed
    Component:  Template system  |                  Version:  3.0
     Severity:  Normal           |               Resolution:  needsinfo
     Keywords:                   |             Triage Stage:  Unreviewed
    Has patch:  0                |      Needs documentation:  0
  Needs tests:  0                |  Patch needs improvement:  0
Easy pickings:  0                |                    UI/UX:  0
Changes (by Carlton Gibson):

 * status:  new => closed
 * resolution:   => needsinfo


 Hi. I'm not sure this is the right place (as yet) for this query.

 It seems like a usage question, rather than a specific bug reports, so I'd
 point you to TicketClosingReasons/UseSupportChannels.

 **Maybe** there's an issue there... if there's a concrete behaviour that's
 wrong but I can't see that from the report.

 > I see the django.db.models.base.Comment.__init__ caches the results.

 `QuerySet` has an internal results cache. `Model.__init__()` creates the
 instance in memory yes, but `ModelIterable` (which is what `.iterator()`
 gives you) instantiates the objects when you iterate it, so that's
 expected behaviour, independent of Jinja vs the DTL.

 If you can narrow this down to something specific that Django is doing
 wrong, we're very happy to have a look.

Ticket URL: <https://code.djangoproject.com/ticket/31582#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Reply via email to