#24705: Exception when negating Q object in annotate
-------------------------------------+-------------------------------------
     Reporter:  karyon               |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  Database layer       |                  Version:  1.8
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     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 martsberger):

 I am seeing this issue as well and the suggested workaround:

 > For the moment, as a workaround, you can stop negating the clause and
 switch the "then" and "default" values to then=True, default=False I
 think.

 Doesn't work for more complex Q objects. For example, a negated Q & a non-
 negated Q.

 {{{#!python
 queryset =
 SomeModel.objects.annotate(value=Case(When(Q(some__field=some_value) &
 ~Q(another__field=another_value))))
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/24705#comment:4>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.b218f1047516c023e9f1d5555533f4e8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to