﻿id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
36508	Asymmetry between exact and iexact when filtering JSON keys against None	Jacob Walls	Clifford Gama	"`exact` and `iexact` vary in their treatment of `None` when looking up JSON key paths:
{{{
optional_param = request.GET.get(""param"", None)
qs1 = Model.objects.filter(json__key=optional_param)
qs2 = Model.objects.filter(json__key__iexact=optional_param)
}}}

[https://dryorm.xterm.info/json-key-filter-none/run fiddle] showing `exact` queries return rows where the json key is null, but `iexact` queries do not (instead, they check for key existence, e.g. `__key__isnull`)

Previous ticket regarding symmetry between `exact` and `iexact`: #21552
Previous ticket regarding `iexact` on JSON key lookups: #27693"	Bug	closed	Database layer (models, ORM)	5.2	Normal	fixed	null, jsonfield	Sage Abdullah	Ready for checkin	1	0	0	0	0	0
