#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):
A wrinkle is that `__exact=None` is pretty
[https://docs.djangoproject.com/en/5.2/ref/models/querysets/#exact clearly
documented] to be synonymous with `__isnull=True`, so by not deprecating
we'd be choosing to memorialize something I found as a user to be a
"gotcha".
> Additionally, on the creation side, supporting nested JSON null like
{"key": JSONNull()} in inserts/updates would require a custom encoder,
which isn’t the case for JSONNull() at the top level.
Would you mind fleshing this out slightly, to make sure I'm catching your
drift?
--
Ticket URL: <https://code.djangoproject.com/ticket/35381#comment:19>
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/01070198e2efbd02-f64ba5c8-f058-48fb-96f2-82931a5ad667-000000%40eu-central-1.amazonses.com.
