#30340: Filtering after `.difference()` does not work
-------------------------------------+-------------------------------------
Reporter: Herman S | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 2.1
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* status: new => closed
* component: Uncategorized => Database layer (models, ORM)
* resolution: => duplicate
Comment:
Duplicate of #28519. The limitation
[https://docs.djangoproject.com/en/dev/ref/models/querysets/#union is
documented]:
In addition, only LIMIT, OFFSET, COUNT(*), ORDER BY, and specifying
columns (i.e. slicing, count(), order_by(), and values()/values_list())
are allowed on the resulting QuerySet. Further, databases place
restrictions on what operations are allowed in the combined queries. For
example, most databases don’t allow LIMIT or OFFSET in the combined
queries.
--
Ticket URL: <https://code.djangoproject.com/ticket/30340#comment:1>
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/066.7e5626b6ae45f02465daa0ee8b98412e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
