#23797: SQL generated for negated F() expressions is incorrect
-------------------------------------+-------------------------------------
Reporter: mssnlayam | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.7
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by mssnlayam):
Is it the case that `filter()` and `exclude()` should produce the
complement of each other? If that is not the case, the obvious queries
would be `WHERE (length = width)` and `WHERE NOT (length = width)`.
If the results should be complimentary, couldn't we use `WHERE (length =
width)` for the filter and `WHERE (length = width)) IS NOT true` for the
exclude. The exclude would be slower, but at least the results would be
consistent.
--
Ticket URL: <https://code.djangoproject.com/ticket/23797#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 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/067.4e0b6a6c51b8c5772d3f7adce06be4a8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
