#30000: Passing QuerySet constructed with .union() causes 
to return wrong values
     Reporter:  thoha                |                    Owner:  nobody
         Type:  Uncategorized        |                   Status:  new
    Component:  Forms                |                  Version:  1.11
     Severity:  Normal               |               Resolution:
     Keywords:  queryset, union,     |             Triage Stage:
  forms                              |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0

Comment (by thoha):

 After some further testing it appears the unexpected behaviour comes from
 the fact that UNION querysets cannot be filtered, which the
 ModelMultipleChoiceField apparently does out of sight. Still, I believe
 that the observed behaviour is undesired, and the field should either
 accept the union queryset and work properly, or raise an exception if a
 union queryset is passed.

 I also found that using

 union_queryset =

 instead of the for-loop results in a queryset that actually works properly
 with the ModelMultipleChoiceField. Based on
 return-broken-queryset-filter-and-get-return-every this StackOverflow

Ticket URL: <https://code.djangoproject.com/ticket/30000#comment:3>
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 
For more options, visit https://groups.google.com/d/optout.

Reply via email to