Repository navigation
[Django 6.1] JSONField key iexact=None lookup returns wrong results on SQL Server #574
Description
Problem
A case-insensitive JSON key lookup against None returns the wrong result set on SQL Server. The failure is silent (no error, wrong rows).
Repro
# value is a JSONField; object has {"j": None} stored
NullableJSONModel.objects.filter(value__j__iexact=None)Expected: rows whose JSON key j is JSON null. Actual: incorrect result set on SQL Server, which has no native JSON null handling for this path.
Scope
Not a 6.1 regression. Sibling to the existing JSONField lookup limitations; the backend JSON handling is not version gated, so this affects all supported Django versions on SQL Server. Django 6.1 added model_fields.test_jsonfield.TestQuerying.test_key_iexact_none, which surfaced it. The test is skipped in testapp/settings.py.
Possible fix
Handle key__iexact=None in the JSON lookup compilation, consistent with the other JSONField null lookups. See the JSONField wiki page.
Activity
[-]JSONField key iexact=None lookup returns wrong results on SQL Server[/-][+][Django 6.1] JSONField key iexact=None lookup returns wrong results on SQL Server[/+]vivekjm commentedon Aug 11, 2026
I’m working on a focused fix for this. I’ll trace the existing JSON null lookup compilation, add regression coverage for
key__iexact=None, and keep the change scoped to the backend SQL generation.bewithgaurav commentedon Aug 11, 2026
Vivek JM (@vivekjm) sure please go ahead - looking forward to the PR :)
FIX: scope JSON iexact=None fix to Django 6.1, stop back-porting to p…