Opened 6 years ago
Closed 6 years ago
#29302 closed New feature (duplicate)
Add support for MySQL's (>=5.6.1) ST_* spatial functions
| Reported by: | Shiv Baishya | Owned by: | nobody |
|---|---|---|---|
| Component: | GIS | Version: | 1.11 |
| Severity: | Normal | Keywords: | MySQL GEOS Spatial |
| Cc: | Shiv Baishya | Triage Stage: | Unreviewed |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
MySQL >=5.6.1 support accurate spatial functions, a.k.a, ST_ functions. Django 1.11 still uses MySQL's old MBR (minimum bounding rectangle) functions.
I am willing to migrate patch for django 1.9.2 to django 1.11 and create a pull request.
Here is an elaborated article on the advantages of the new MySQL's ST_ functions.
Related tickets
- https://code.djangoproject.com/ticket/22423 (4 years old, is anyone working on this?)
- https://code.djangoproject.com/ticket/27574
Change History (5)
comment:1 by , 6 years ago
| Cc: | added |
|---|---|
| Keywords: | Spatial added |
comment:2 by , 6 years ago
| Description: | modified (diff) |
|---|
comment:3 by , 6 years ago
comment:4 by , 6 years ago
| Description: | modified (diff) |
|---|
comment:5 by , 6 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
| Summary: | Support for MySQL's (>=5.6.1) accurate spatial functions → Add support for MySQL's (>=5.6.1) ST_* spatial functions |
Note:
See TracTickets
for help on using tickets.
This looks like a duplicate of #22423. Have I misunderstood the issue? Did you see the patch in that ticket? Maybe you can update that patch and fix the failure. If so, please send the pull request to master. Per our supported versions policy. Django 1.11 only receives security and data loss fixes at this time.