#23797: SQL generated for negated F() expressions is incorrect
-------------------------------------+-------------------------------------
Reporter: Suriya Subramanian | Owner: Jacob
| Walls
Type: Bug | Status: assigned
Component: Database layer | Version: 1.7
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls):
* needs_better_patch: 1 => 0
Comment:
Updated patch to address review comments.
It is worth mentioning the patch only addresses the case where both
columns are nullable. If the source column is not nullable and the target
column of the F() expression is nullable, exclude() still does not return
records where the F() expression evaluates to NULL.
I'm open to thoughts on whether this ticket should be left open to address
that unhandled case, or whether another ticket should track it.
--
Ticket URL: <https://code.djangoproject.com/ticket/23797#comment:12>
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/067.b44bdc4266ae6ce3caca4452d983d4f7%40djangoproject.com.
