Changes between Initial Version and Version 1 of Ticket #35381, comment 21


Ignore:
Timestamp:
Aug 26, 2025, 7:32:07 AM (3 weeks ago)
Author:
Jacob Walls

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #35381, comment 21

    initial v1  
    77... which I think is an acceptable trade-off for top-level JSON null.
    88
    9 For nulls in key/value pairs, as in your example, I think it's still an acceptable trade-off, as long as we are not *removing* the ability of users to store python `None` in key/value pairs. The plan I see from the above comments is just to deprecate & change the behavior of filtering on `None` in key/value pairs.
     9For nulls in key/value pairs, as in your example, I think it's still an acceptable trade-off, as long as we are not *removing* the ability of users to store python `None` in key/value pairs. The plan I see from the above comments is just to deprecate & change the behavior of filtering on `None` in key/value pairs. (EDIT: not really, see comment:22 and comment:23 for updates.)
Back to Top