#34959: Q(a=b) and Exact(a, b) handle NULLs differently
-------------------------------------+-------------------------------------
Reporter: Roman Odaisky | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Normal | Resolution:
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 Simon Charette):
It seems like the exact same bug as #34959 that has
[https://github.com/django/django/pull/16817/ a proposed implementation
that allows expressions to denote how they handle nulls].
--
Ticket URL: <https://code.djangoproject.com/ticket/34959#comment:1>
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/0107018bb7dd2d98-c3ae507e-c427-4920-9403-83cf7862838e-000000%40eu-central-1.amazonses.com.
