#19652: Fix for #19524 introduced a backward compatiblity issue with related
managers on 1.5.X
-------------------------------------+-------------------------------------
Reporter: charettes | Owner: nobody
Type: Bug | Status: new
Component: ORM aggregation | Version:
Severity: Release blocker | 1.5-beta-1
Keywords: none EmptyQuerySet | Resolution:
none | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by akaariai):
* stage: Unreviewed => Accepted
Comment:
A pk can't be NULL, but if you use to_field, then you could have NULLs on
both sides. We definitely want the semantics of SQL's JOIN ON (lhs.fk_val
= rhs.to_field). This means that if either/both of those are NULL, then
the result is "no match". (SQL's funny trinary boolean logic, NULL = NULL
=> UNKNOWN.)
If we go an try to change this we will have endless amount of problems.
--
Ticket URL: <https://code.djangoproject.com/ticket/19652#comment:4>
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
