#34570: QuerySet.defer() raises an AttributeError when the field is
ManyToManyField or GenericForeignKey
-------------------------------------+-------------------------------------
Reporter: Paco Martínez | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: contenttypes, | Triage Stage: Ready for
defer, manytomanyfield, | checkin
genericforeignkey |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"201d29b3719ef15637648be7bd947ef90a66ab55" 201d29b]:
{{{
#!CommitTicketReference repository=""
revision="201d29b3719ef15637648be7bd947ef90a66ab55"
[4.2.x] Fixed #34570 -- Silenced noop deferral of many-to-many and GFK.
While deferring many-to-many and GFK has no effect, the previous
implementation of QuerySet.defer() ignore them instead of crashing.
Regression in b3db6c8dcb5145f7d45eff517bcd96460475c879.
Thanks Paco Martínez for the report.
Backport of 99e5dff737cd20b12d060e4794e097063b61ec40 from main
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/34570#comment:6>
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/01070188286fe3fc-808ac3cf-8d29-4ce3-8b72-e88a16e789bb-000000%40eu-central-1.amazonses.com.
