#25284: Regression when filtering by subquery
-------------------------------------+-------------------------------------
Reporter: Naddiseo | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by akaariai):
This seems to have been non-documented and non-tested feature (probably
accidental, too). Changing the behavior definitely counts as a bug fix
(even more for cases where doing `qs.filter(related__range=otherqs)` would
result in an IN lookup).
Lets advertise this as loudly as we can in the release notes as a breaking
change. It is going to be hard to find these cases in your code manually,
but I think 99% of such cases will result in an error in 1.9, as some_id =
(select id from other model) will result in an error if there are more
than one id returned by the subquery.
--
Ticket URL: <https://code.djangoproject.com/ticket/25284#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.dbb2097713d522b75aa818e765d09a5a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
