#35381: Provide `JSONNull` expression to represent JSON `null` value
-------------------------------------+-------------------------------------
Reporter: Olivier Tabone | Owner: Clifford
| Gama
Type: New feature | Status: assigned
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls):
Oh this clarifies things for me. I'll edit my recent comments to avoid
suggesting there was consensus to change the behavior of filtering on
`None` in key values, since it sounds like that was only proposed in
comment:4, and later as Clifford points out, in the triage decision on
#36508, but now we have multiple people with misgivings about doing that.
Having just left a project that managed most of its data in JSONFields, I
can offer that auditing the behavior of key=var lookups everywhere to
figure out what's intended when `var` is possibly `None` would be a
daunting expense.
Re: the "gotcha" of `exact=None` and `isnull=True` not being invariant, we
can just doc it clearly.
--
Ticket URL: <https://code.djangoproject.com/ticket/35381#comment:23>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070198e65ac15e-536b5551-7db2-4a86-a0cf-fa93fb4a333d-000000%40eu-central-1.amazonses.com.
