#29302: Support for MySQL's (>=5.6.1) accurate spatial functions
               Reporter:  Shiv Baishya  |          Owner:  nobody
                   Type:  New feature   |         Status:  new
              Component:  GIS           |        Version:  1.11
               Severity:  Normal        |       Keywords:  MySQL GEOS
           Triage Stage:  Unreviewed    |      Has patch:  1
    Needs documentation:  0             |    Needs tests:  0
Patch needs improvement:  0             |  Easy pickings:  0
                  UI/UX:  0             |
 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 my
 [https://github.com/shiviser/django/tree/1.9.2_ST_build patch for django
 1.9.2] to django 1.11 and create a pull request.
 Here is an elaborated [https://www.percona.com/blog/2013/10/21/using-the-
 new-mysql-spatial-functions-5-6-for-geo-enabled-applications/ article] on
 the advantages of the new MySQL's **ST_ functions**.
 **Related tickets**
 * https://code.djangoproject.com/ticket/22423
 * https://code.djangoproject.com/ticket/27574

Ticket URL: <https://code.djangoproject.com/ticket/29302>
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 
For more options, visit https://groups.google.com/d/optout.

Reply via email to