#30124: QuerySet.only() on reverse many-to-one relationship causes extra
database
queries
-------------------------------------+-------------------------------------
Reporter: Beda Kosata | Owner: Dan Davis
Type: Bug | Status: assigned
Component: Database layer | Version: 2.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Dan Davis):
New idea - in the case of a select_related(), then the natural expectation
is that only will also apply to fields in the related model. To finish
this, I will need to understand better how the select tuple in
`django.db.models.sql.query.Query` is populated, and when. I know it is
deferred to the end. I will check.
--
Ticket URL: <https://code.djangoproject.com/ticket/30124#comment:5>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.20da4bf06f682d5467d0ba94d07bb91c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
