#37171: Targeting a subquery with __exact requires limiting to one result even
when
wrapped by explicit Subquery
-------------------------------------+-------------------------------------
Reporter: Mark Baird | Owner: (none)
Type: Bug | Status: closed
Component: Database layer | Version: 6.0
(models, ORM) |
Severity: Normal | Resolution: invalid
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 Jacob Walls):
In this case the error message is clear ("an exact lookup must be limited
to one result"), so I'm not sure a release note would provide additional
useful information. It would be a different situation if this were a
breaking change, but Django is just behaving as
[https://docs.djangoproject.com/en/dev/ref/models/expressions/#limiting-
the-subquery-to-a-single-row documented], and in general we don't document
bugfixes that bring Django's behavior in greater alignment with its docs.
--
Ticket URL: <https://code.djangoproject.com/ticket/37171#comment:3>
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 visit
https://groups.google.com/d/msgid/django-updates/0107019ed0e86d12-a5b321b2-4a98-48a6-82bf-403b43960c06-000000%40eu-central-1.amazonses.com.
