#26019: Incorrect query generated when combining querysets refering to different
fields under the same alias.
-------------------------------------+-------------------------------------
Reporter: mssnlayam | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(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 shaib):
If and when we do teach it to use `UNION ALL`, and since `distinct()` was
mentioned in the OP's example, we should probably do something to get
distinct queries to use `UNION` instead of `UNION ALL`.
--
Ticket URL: <https://code.djangoproject.com/ticket/26019#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.d13391cf2733c2fd8ed7a53138995863%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
