#31324: Filter JSONField using `=None`
-------------------------------------+-------------------------------------
Reporter: Nikolay Tretyak | Owner: Nikolay
| Tretyak
Type: Bug | Status: assigned
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):
* cc: sage (added)
* version: 2.2 => 3.0
Comment:
I'm not sure if that's an issue, I would say that it's decision made to
support `NULL` (SQL) and `null` (JSON). We support storing primitives in
`JSONField` so also `null` which is not the same as `NULL` in the sense of
SQL. We also decided to keep this behavior in new `JSONField`'s, see
[https://github.com/django/django/pull/12392/files#diff-
8306d3c952976534470d55bf80dff66bR245-R266
test_json_null_different_from_sql_null()] test and
[https://github.com/django/django/pull/11452#discussion_r335375254 a short
discussion]. This could be documented better in
[https://github.com/django/django/pull/12392 PR 12392].
IMO it's invalid ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/31324#comment:6>
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/067.61458db88247f54228569e5194316e80%40djangoproject.com.
