#28199: `Subquery` in __in filter generating invalid SQL
-------------------------------------+-------------------------------------
Reporter: Murray | Owner: nobody
Christopherson |
Type: Bug | Status: closed
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: subquery | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"9b9a81024a4955d6d3fb9f440b89567bb1634090" 9b9a810]:
{{{
#!CommitTicketReference repository=""
revision="9b9a81024a4955d6d3fb9f440b89567bb1634090"
[1.11.x] Fixed #28199 -- Fixed Subquery generating unnecessary/invalid
CAST.
Thanks Simon Charette for the fix.
Backport of f04495521ade8a2befc1aca70dd0a2c7aad4c987 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28199#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/067.e084500179a71a08432065311e8f0f6b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
