#34603: ~Q() incorrectly interpreted as full rather than empty
-------------------------------------+-------------------------------------
Reporter: Anders Kaseorg | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution: wontfix
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 Mariusz Felisiak):
* status: new => closed
* resolution: => wontfix
Comment:
I understand how the current logic works (there is no need for a long
examples), and I'm not sure how it justifies that `~Q()` should return an
empty queryset. `Q()` is "nothing", if you will negate "nothing" you will
still get "nothing". This is rather a philosophical discourse.
I appreciate you'd like to reopen the ticket, but please
[https://docs.djangoproject.com/en/stable/internals/contributing/triaging-
tickets/#closing-tickets follow the triaging guidelines with regards to
wontfix tickets] and take this to DevelopersMailingList, where you'll
reach a wider audience and see what other think.
--
Ticket URL: <https://code.djangoproject.com/ticket/34603#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701886beff3bb-779dfff4-61cd-4083-9ccd-332b9d64989a-000000%40eu-central-1.amazonses.com.
