#28896: GeoDjango PointField fails to generate query if filtering on a NULL
value
-------------------------------------+-------------------------------------
Reporter: William Li | Owner: Sergey
| Fedoseev
Type: Bug | Status: assigned
Component: GIS | Version: 2.0
Severity: Release blocker | Resolution:
Keywords: PointField | Triage Stage: Ready for
GeoDjango | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"10bfa876be59feec24bb6a40fa11bece808ee405" 10bfa876]:
{{{
#!CommitTicketReference repository=""
revision="10bfa876be59feec24bb6a40fa11bece808ee405"
Refs #27985 -- Reallowed using __exact=None as an alias for __isnull=True
if a custom lookup class with lookup_name != None is registered as the
exact lookup.
Regression in 58da81a5a372a69f0bac801c412b57f3cce5f188 and prerequisite
for refs #28896.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28896#comment:6>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/061.c3e39d5f00c50b570093fc266eca8686%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
