#36508: Asymmetry between exact and iexact when filtering JSON keys against None
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Clifford
| Gama
Type: Bug | Status: assigned
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: null, jsonfield | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls):
We might want to just fix without a deprecation(*), since there is no
"upgrade path". If we warn about this, and you discover you really wanted
the "new" behavior all along, the only answer would be to just wait, which
isn't great.
(*) but doc it as a minor incompatible change?
I feel like most who have gone to the trouble to specify `iexact` wouldn't
expect `iexact` to simply check key existence, and thus will want the
"new" behavior.
--
Ticket URL: <https://code.djangoproject.com/ticket/36508#comment:10>
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 visit
https://groups.google.com/d/msgid/django-updates/01070198e767d05e-3ab01592-01b4-451d-939f-b876396addf5-000000%40eu-central-1.amazonses.com.
