#26789: ORM produces query with NULL instead of empty geometry
----------------------------+--------------------------------------
Reporter: sir-sigurd | Owner: sir-sigurd
Type: Bug | Status: assigned
Component: GIS | Version: 1.9
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------------------------
Changes (by rcoup):
* has_patch: 0 => 1
Comment:
WIP pull request at https://github.com/django/django/pull/6934
Current approach passes empty to the DB and lets it decide whether to
accept it.
Issues for discussion here:
* `POINT EMPTY` has a GEOS error on save for me w/ GEOS3.5.0 on OSX. We
could workaround that.
* `POLYGON EMPTY` has a PostGIS error on save for me w/ Postgis 2.2.2
(Postgres 9.5) on OSX
* Should we delegate to backends to "check" whether a geometry is save-
able, or pass it through to the DB?
* Need to test on the other DB backends, @jitai is that possible for you
to do Oracle? Might need a `@no_oracle` on the test.
I considered an alternative approach of "fixing" falsey/truthy evaluation
of geometries and use that as a proxy to save. Though IMO an empty geom
could quite logically evaluate to False though it should be saved.
--
Ticket URL: <https://code.djangoproject.com/ticket/26789#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/068.02a4e742231cb53ed72e3402b3d6388e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
