[Django] #29302: Support for MySQL's (>=5.6.1) accurate spatial functions
Django
----------------------------------------+----------------------------
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,
[https://dev.mysql.com/doc/refman/5.6/en/spatial-function-reference.html
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.
Django
Reporter: Shiv Baishya | Owner: nobody
Type: New feature | Status: new
Component: GIS | Version: 1.11
Keywords: MySQL GEOS Spatial | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by Shiv Baishya):
* cc: Shiv Baishya (added)
* keywords: MySQL GEOS => MySQL GEOS Spatial
--
Ticket URL: <https://code.djangoproject.com/ticket/29302#comment:1>
Django
Reporter: Shiv Baishya | Owner: nobody
Type: New feature | Status: new
Component: GIS | Version: 1.11
Keywords: MySQL GEOS Spatial | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Description changed by Shiv Baishya:
Old description:
> MySQL >=5.6.1 support accurate spatial functions, a.k.a,
> [https://dev.mysql.com/doc/refman/5.6/en/spatial-function-reference.html
> 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
New description:
MySQL >=5.6.1 support accurate spatial functions, a.k.a,
[https://dev.mysql.com/doc/refman/5.6/en/spatial-function-reference.html
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 (4 years old, is anyone
working on this?)
* https://code.djangoproject.com/ticket/27574
--
--
Ticket URL: <https://code.djangoproject.com/ticket/29302#comment:2>
Django
Reporter: Shiv Baishya | Owner: nobody
Type: New feature | Status: new
Component: GIS | Version: 1.11
Keywords: MySQL GEOS Spatial | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Comment (by Tim Graham):
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
[https://docs.djangoproject.com/en/dev/internals/release-process
/#supported-versions supported versions policy]. Django 1.11 only receives
security and data loss fixes at this time.
--
Ticket URL: <https://code.djangoproject.com/ticket/29302#comment:3>
Django
Reporter: Shiv Baishya | Owner: nobody
Type: New feature | Status: new
Component: GIS | Version: 1.11
Keywords: MySQL GEOS Spatial | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Description changed by Shiv Baishya:
Old description:
> MySQL >=5.6.1 support accurate spatial functions, a.k.a,
> [https://dev.mysql.com/doc/refman/5.6/en/spatial-function-reference.html
> 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 (4 years old, is anyone
> working on this?)
> * https://code.djangoproject.com/ticket/27574
New description:
MySQL >=5.6.1 support accurate spatial functions, a.k.a,
[https://dev.mysql.com/doc/refman/5.6/en/spatial-function-reference.html
ST_ functions]. Django 1.11 still uses MySQL's old MBR (minimum bounding
rectangle) functions.
\\
I am willing to migrate
[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 (4 years old, is anyone
working on this?)
* https://code.djangoproject.com/ticket/27574
--
--
Ticket URL: <https://code.djangoproject.com/ticket/29302#comment:4>
Django
------------------------------------+--------------------------------------
Reporter: Shiv Baishya | Owner: nobody
Component: GIS | Version: 1.11
Severity: Normal | Resolution: duplicate
Keywords: MySQL GEOS Spatial | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by Tim Graham):
* status: new => closed
* resolution: => duplicate
--
Ticket URL: <https://code.djangoproject.com/ticket/29302#comment:5>