#25446: Can't use PostGIS function ST_OrderingEquals with GeoDjango
-----------------------------+------------------------------------
Reporter: ezheidtmann | Owner: nobody
Type: New feature | Status: new
Component: GIS | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+------------------------------------
Comment (by ezheidtmann):
Thank you! I updated the workaround to fix a couple edge cases. And I will
look forward to 1.9.
While we're on the topic, what do you think about changing the "exact"
lookup to use ST_OrderingEquals? This would match the behavior of GEOS
LineString objects but I am not sure of the broader implications of that
change. Perhaps SpatiaLite does not offer an equivalent, so we cannot bake
it into Django?
Thanks,
-Evan
--
Ticket URL: <https://code.djangoproject.com/ticket/25446#comment:3>
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/069.f82213248a6b8b5213cdd93c48318912%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
