#33769: F() expressions - OperationalError
-------------------------------+------------------------------------
     Reporter:  Pablo          |                    Owner:  nobody
         Type:  Bug            |                   Status:  closed
    Component:  Documentation  |                  Version:  3.2
     Severity:  Normal         |               Resolution:  invalid
     Keywords:                 |             Triage Stage:  Accepted
    Has patch:  0              |      Needs documentation:  0
  Needs tests:  0              |  Patch needs improvement:  0
Easy pickings:  0              |                    UI/UX:  0
-------------------------------+------------------------------------

Comment (by Simon Charette):

 I didn't run proper bisecting but by comparing the queries the only
 semantic difference between both is wrapping of the right-hand-side of the
 `IN` operator in parentheses.

 So I suspect this was broken by 3a505c70e7b228bf1212c067a8f38271ca86ce09
 in 3.0 and fixed back in 4.0 by 170b006ce82b0ecf26dc088f832538b747ca0115
 for reasons unrelated to the rationale mentioned here.

 All that to say that we don't explicitly support/test for
 `__in=single_valued_expression` and this was inadvertently broken in 3.0
 and fixed later on.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/33769#comment:7>
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/010701813fdb52e5-0296f0a7-8c6e-4d30-8653-0f2ecd44c343-000000%40eu-central-1.amazonses.com.

Reply via email to