#24688: Add Oracle support for new-style GIS functions ---------------------------------------+------------------------ Reporter: claudep | Owner: nobody Type: New feature | Status: new Component: GIS | Version: master Severity: Normal | Keywords: oracle Triage Stage: Accepted | Has patch: 0 Needs documentation: 0 | Needs tests: 0 Patch needs improvement: 0 | Easy pickings: 0 UI/UX: 0 | ---------------------------------------+------------------------ In #24214, GIS-specific QuerySet methods have been replaced by database functions, for all backends except the Oracle one.
Until now, nobody volunteered to do that part. We might drop the Oracle GIS support for 1.9 if noone is interested to maintain it. Commits 44bdbbc316e4e0b2f5d8c7767d04924c9e00f2da (Spatialite) and 71e20814fcb5983bdc96a6b15765b8f6abd11542 (MySQL) are good starting point to evaluate the needed work. -- Ticket URL: <https://code.djangoproject.com/ticket/24688> 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 django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/050.f981e6abf8ecdb77d8dda06d978469d2%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.