#31135: OuterRef generates invalid SQL with __in filter.
-------------------------------------+-------------------------------------
     Reporter:  Bernd Wechner        |                    Owner:  nobody
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  3.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 Bernd Wechner):

 Replying to [comment:5 Mariusz Felisiak]:
 > Replying to [comment:4 Vasili Korol]:
 > > I bumped into this after upgrading from 2.2 to 3.2. Not sure why was
 this ticket closed, the issue is still there!
 >
 > It was closed because this usage has never been officially supported.

 It remains a bug that it produces invalid SQL where a prior version did
 not, and not a sensible exception - causing much wasted time on the part
 of anyone who used the old (unsupported but functional) syntax.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/31135#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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070180b2110fbb-ef28e5cc-2bf3-4e3b-8639-9952e18f319c-000000%40eu-central-1.amazonses.com.

Reply via email to