#19652: Fix for #19524 introduced a backward compatiblity issue with related
managers on 1.5.X
-------------------------------------+-------------------------------------
Reporter: charettes | Owner: charettes
Type: Bug | Status: closed
Component: ORM aggregation | Version:
Severity: Release blocker | 1.5-beta-1
Keywords: none EmptyQuerySet | Resolution: fixed
none | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Anssi Kääriäinen <akaariai@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"f4132140f52c88b67d11743d4062a9d455959ffc"]:
{{{
#!CommitTicketReference repository=""
revision="f4132140f52c88b67d11743d4062a9d455959ffc"
[1.5.x] Fixed #19652 -- Fixed .none() regression in related fields
The regression was caused by using .none() when querying for related
models, and the origin field's value was None. This resulted in missing
custom related manager subclass as .none() returns plain QuerySet.
This isn't backport from master, in master .none() correctly preserves
the queryset's class.
Patch provided by Simon Charette, with some minor polish by committer.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/19652#comment:12>
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
