#34612: QuerySet.only() doesn't work with select_related() on a reverse
OneToOneField relation.
-------------------------------------+-------------------------------------
Reporter: Ian Cubitt | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Release blocker | Resolution: fixed
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
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"2cf76f2d5d1aa16acfadaf53db3d30128a34b088" 2cf76f2d]:
{{{
#!CommitTicketReference repository=""
revision="2cf76f2d5d1aa16acfadaf53db3d30128a34b088"
Fixed #34612 -- Fixed QuerySet.only() crash on reverse relationships.
Regression in b3db6c8dcb5145f7d45eff517bcd96460475c879.
Thanks Ian Cubitt for the report.
This also corrected test_inheritance_deferred2() test which was
previously properly defined and marked as an expected failure but was
then wrongly adjusted to mask the lack of support for per-alias
deferral that was fixed by #21204.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/34612#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070188786bf523-eaf61e18-4e3e-45c1-a782-9bdd22eb08d9-000000%40eu-central-1.amazonses.com.
