#35381: Regression on json null value constraints in django 4.2
-------------------------------------+-------------------------------------
Reporter: Olivier Tabone | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 5.0
(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 Natalia Bidart):
Thank you Simon. In my view, and in an ideal situation, we shouldn't allow
"anywhere" to use `None` as the json's `null`. I think we should reserve
`None` only to represent SQL's `NULL`, and have a representation for the
(string) json's `null` (I understand this matches the new `JSONNull`
expression you are proposing).
> Should we only do this at the top level to still allow
`jsonfield__key=None` to filter against null keys?
I would say no, because it then gets very confusing.
> An alternative would be to introduce a `__jsonnull` lookup.
Would this lookup allow further lookups to be chained?
--
Ticket URL: <https://code.djangoproject.com/ticket/35381#comment:4>
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/0107018f5304d6c3-0b343c68-e274-4a3b-badd-fb16bb93739e-000000%40eu-central-1.amazonses.com.
