#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
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
Replying to [comment:4 Anders Kaseorg]:
> There’s an important difference between ''including'' nothing and
''excluding'' nothing.
TBH, I don't see any difference between including and excluding a void.
> I know this is a dense explanation that’s hard to digest in this
abstract form. But the rules of formal logic do give us a right answer
here; this is not some ambiguous question of philosophy.
As far as I'm aware, that's not true. Rules of mathematical logic don't
give us a clear answer how to negate "nothing". For example, `NOT NULL` is
`NULL`, it doesn't have a logical evaluation. Again, start a discussion on
the Django Forum or on the mailing list, if you don't agree.
--
Ticket URL: <https://code.djangoproject.com/ticket/34603#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701886c4ee95a-89484af1-fe65-4fdf-a417-82b40c8acafd-000000%40eu-central-1.amazonses.com.
