#30532: Union queryset should raise on filter() and exclude(). -------------------------------------+------------------------------------- Reporter: cgthayer | Owner: nobody Type: | Status: closed Cleanup/optimization | Component: Database layer | Version: master (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 felixxm):
* status: new => closed * type: Uncategorized => Cleanup/optimization * component: Uncategorized => Database layer (models, ORM) * version: 2.2 => master * resolution: => duplicate Comment: Yes `filter()` and `exclude()` are unsupported but doesn't raise an error yet. As [https://docs.djangoproject.com/en/stable/ref/models/querysets/#union per the documentation], ''"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."''. Duplicate of #27995. See also a ticket #28519 to support these features. -- Ticket URL: <https://code.djangoproject.com/ticket/30532#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 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/066.94f4c4fce2b78fea706ad8e7007d2c00%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.