#32252: Using __isnull=True on a KeyTransform should not match JSON null on
SQLite
and Oracle
-------------------------------------+-------------------------------------
Reporter: sage | Owner: sage
Type: Bug | Status: closed
Component: Database layer | Version: 3.1
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"a891e1bb0a3e1b29a461784cd0bf717513e72f19" a891e1b]:
{{{
#!CommitTicketReference repository=""
revision="a891e1bb0a3e1b29a461784cd0bf717513e72f19"
[3.1.x] Fixed #32252 -- Fixed __isnull=True on key transforms on SQLite
and Oracle.
__isnull=True on key transforms should not match keys with NULL values.
Backport of 8d7085e0fd004af5431389f3d903aba6220d7957 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32252#comment:5>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/067.b8e5602cb85010d60da3223f5d99a5c3%40djangoproject.com.
