#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 Simon Charette):

 I share your position Jacob.

 To me the ambiguity of what to do with `None` only exists for top level
 values of `JSONField(null=True)`; there's no ambiguity for key values as
 it always mean JSON `null`.

 To make it clear I also think that `filter(data__key=None)` should
 continue to match JSON `null` and I'm not opposed to supporting
 `filter(data__key=JSONNull())` while I don't see much benefits to it.
-- 
Ticket URL: <https://code.djangoproject.com/ticket/35381#comment:22>
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/01070198e6424418-e0d92528-ab27-4343-8fa7-0b2b69188409-000000%40eu-central-1.amazonses.com.

Reply via email to