#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 Mark Baird):
I see. The addition of [:1] in the subquery does fix it, thanks for that.
So even if this isn't a bug, I still think the breaking change should be
mentioned in the Django changelog so people running into this can see that
it is an intended change? The ticket you reference seems to be
specifically for composite primary keys, which I'm not using here at all,
so it is certainly not obvious to me that the change in that ticket would
have caused this change in behavior.
--
Ticket URL: <https://code.djangoproject.com/ticket/37171#comment:2>
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/0107019ed0dd72f4-08ad0174-b970-4a8f-9ef2-520d5e443b63-000000%40eu-central-1.amazonses.com.
