#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
-------------------------------------+-------------------------------------
Changes (by GitHub <noreply@…>):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"f04495521ade8a2befc1aca70dd0a2c7aad4c987" f044955]:
 {{{
 #!CommitTicketReference repository=""
 revision="f04495521ade8a2befc1aca70dd0a2c7aad4c987"
 Fixed #28199 -- Fixed Subquery generating unnecessary/invalid CAST.

 Thanks Simon Charette for the fix.
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/28199#comment:5>
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.458a25458e04fa54d1ceb5f5966982b3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to