#36508: Asymmetry between exact and iexact when filtering JSON keys against None
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: (none)
Type: Bug | Status: new
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: null, jsonfield | 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):
I feel like this falls into the same bucket, or at least very close, to
the other issues relating to trying to do the right thing when `None` is
provided to `JSONField` and that the solution lies in making `None` always
translate to `NULL` and require `JSONNull` in cases where JSON `null` is
required.
--
Ticket URL: <https://code.djangoproject.com/ticket/36508#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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701980ec68264-ff167618-d4aa-4582-ae44-569ac9af73a8-000000%40eu-central-1.amazonses.com.
