#27985: Converting `Foo.objects.filter(bar=None)` to an `IsNull` too early.
-------------------------------------+-------------------------------------
Reporter: Jarek Glowacki | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: sql None NULL | Triage Stage: Accepted
transform |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jarek Glowacki):
[https://github.com/django/django/compare/master...jarekwg:ticket_27985
Here's a failing testcase] for now; will have a crack at writing a patch
soon..
Also realised it gets even messier for the `.exclude()` case, where it
[https://github.com/django/django/blob/master/django/db/models/sql/query.py#L1214-L1229
adds an extra query].
This causes a mutually exclusive pair of conditions, that'll always
evaluate to false.
It does this:
`Foo.objects.exclude(bar='')` -> `... WHERE NOT ("foo"."bar" = NULL AND
"foo"."bar" IS NOT NULL)`
Instead of just
`Foo.objects.exclude(bar=None)` -> `... WHERE NOT ("foo"."bar" IS NULL)`
--
Ticket URL: <https://code.djangoproject.com/ticket/27985#comment:2>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.27fc00357777be2ba768244e151317df%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
