Opened 10 years ago
Last modified 5 years ago
#22423 closed New feature
Geodjango spatial functions should leverage mysql 5.6 spatial functions. — at Initial Version
| Reported by: | visu | Owned by: | visu |
|---|---|---|---|
| Component: | GIS | Version: | dev |
| Severity: | Normal | Keywords: | gis, mysql, |
| Cc: | visumrs@… | Triage Stage: | Ready for checkin |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Hi,
Starting from 5.6 version, mysql implemented spatial functions properly.
(ie, similar to postgis, mysql also supports ST_Contains, ST_Within and other ST_ queries.)
http://dev.mysql.com/doc/refman/5.6/en/functions-for-testing-spatial-relations-between-geometric-objects.html#function_st-contains
Geodjango currently implements polycontains and other queries for mysql as "MBRContains" instead of "Contains"
https://docs.djangoproject.com/en/dev/ref/contrib/gis/geoquerysets/#std:fieldlookup-gis-contains
This needs to be fixed.
related Ticket :
Note:
See TracTickets
for help on using tickets.