#17668: prefetch_related does not work in in_bulk
-------------------------------------+-------------------------------------
     Reporter:  gurets@…             |                    Owner:  lukeplant
         Type:  Uncategorized        |                   Status:  new
    Component:  Database layer       |                  Version:
  (models, ORM)                      |  1.4-alpha-1
     Severity:  Release blocker      |               Resolution:
     Keywords:  prefetch_related,    |             Triage Stage:  Accepted
  in_bulk                            |      Needs documentation:  0
    Has patch:  0                    |  Patch needs improvement:  0
  Needs tests:  0                    |                    UI/UX:  0
Easy pickings:  0                    |
-------------------------------------+-------------------------------------

Comment (by akaariai):

 I am OK with the above.

 Should there be a way to see if there are prefetches? It would be cheap to
 add a way to see the current prefetches, this would give a chance to skip
 the .iterator() call if there are prefetches defined.

 Or maybe just document the current behavior, fix in_bulk and be done with
 it. If somebody complains, add a way to check the prefetches then. I have
 a feeling I have wasted enough everybody's time on this issue already...

-- 
Ticket URL: <https://code.djangoproject.com/ticket/17668#comment:8>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to