#28896: GeoDjango PointField fails to generate query if filtering on a NULL
value
--------------------------------------+------------------------------------
Reporter: William Li | Owner: nobody
Type: Bug | Status: new
Component: GIS | Version: 2.0
Severity: Release blocker | Resolution:
Keywords: PointField GeoDjango | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Tim Graham):
* keywords: QuerySet.extra PointField GeoDjango => PointField GeoDjango
* cc: Sergey Fedoseev (added)
* component: Database layer (models, ORM) => GIS
* severity: Normal => Release blocker
* stage: Unreviewed => Accepted
Comment:
Bisected to 58da81a5a372a69f0bac801c412b57f3cce5f188. I would imagine that
`__isnull=True` works, but we should either restore the old behavior of
accepting `None` or document the backwards incompatibility.
--
Ticket URL: <https://code.djangoproject.com/ticket/28896#comment:2>
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.bfe74c075d832738a7b2f2de964f90b1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
