#36593: Deprecate select_related() with no arguments
-------------------------------------+-------------------------------------
     Reporter:  Adam Johnson         |                    Owner:  Adam
         Type:                       |  Johnson
  Cleanup/optimization               |                   Status:  assigned
    Component:  Database layer       |                  Version:  dev
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:  Ready for
                                     |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls <jacobtylerwalls@…>):

 In [changeset:"0c634de4e6950ec6fb83ab420b4af9c645b28acd" 0c634de]:
 {{{#!CommitTicketReference repository=""
 revision="0c634de4e6950ec6fb83ab420b4af9c645b28acd"
 Refs #36593 -- Made ModelAdmin.list_select_related = False more efficient.

 This change makes `list_select_related = False` avoid unnecessary joins by
 only
 selecting the related fields that are actually used in `list_display`.
 Consequently, it avoids one code path that calls
 `QuerySet.select_related()`
 with no arguments, which is targeted for deprecation.
 }}}
-- 
Ticket URL: <https://code.djangoproject.com/ticket/36593#comment:7>
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 [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/django-updates/0107019e17e21ed8-42e6bffe-03a7-47ab-92c3-778a69a0f6f6-000000%40eu-central-1.amazonses.com.

Reply via email to