#16893: negation of Q object returns the same thing
-------------------------------------+-------------------------------------
Reporter: morgy.wahl@… | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.2
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Accepted
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
* resolution: => wontfix
Comment:
As mentioned by Baptiste, the current behavior is
[https://github.com/django/django/blob/e7fa8aff432a90b6df9914d63aad239164b6b4d4/tests/queries/tests.py#L1731-L1748
tested] and expected (IMO). Filtering by an empty condition `Q()` and
negation of an empty condition `~Q()` should return all objects, because
negation of an empty condition is still an empty condition.
You can start a discussion on DevelopersMailingList if you don't agree.
--
Ticket URL: <https://code.djangoproject.com/ticket/16893#comment:7>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/078.9d13878d66ecd6cd4757893c15c8a8c2%40djangoproject.com.
