[Django] #37320: Add support for ST_Transform on MySQL

[Django]

#37320: Add support for ST_Transform on MySQL
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Type: New
| feature
Status: new | Component: GIS
Version: 6.1 | Severity: Normal
Keywords: mysql, transform, | Triage Stage:
srs | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
MySQL has an `ST_Transform` function since 8.0.13, and "all" Cartesian
transforms are
​[https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-32.html#:~:text=now%20supports%20all%20Cartesian%20projections
supported since 8.0.32], so we should add support for the `Transform` geo
function.

[https://dev.mysql.com/doc/refman/9.7/en/spatial-operator-functions.html
#function_st-transform docs]

It is likely that we should first tackle #33120 (implement Spatial
Reference System (SRS)) to avoid rework, but an implementer could confirm.

Gates on `supports_transform` should be checked to see if they can use the
new functionality safely, or if they should fallback to the old read/write
SRID-0 behavior described in #27574.

This is a blocker for fixing #27574, which is a pain point that has come
up on the forum a couple times.
--
Ticket URL: <https://code.djangoproject.com/ticket/37320>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#37320: Add support for ST_Transform on MySQL
-------------------------------------+-------------------------------------

Reporter: Jacob Walls | Owner: (none)

Type: New feature | Status: new
Component: GIS | Version: 6.1

Severity: Normal | Resolution:

Keywords: mysql, transform, | Triage Stage:
srs | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Description changed by Jacob Walls:

Old description:

> MySQL has an `ST_Transform` function since 8.0.13, and "all" Cartesian
> transforms are
> ​[https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-32.html#:~:text=now%20supports%20all%20Cartesian%20projections
> supported since 8.0.32], so we should add support for the `Transform` geo
> function.
>
> [https://dev.mysql.com/doc/refman/9.7/en/spatial-operator-functions.html
> #function_st-transform docs]
>
> It is likely that we should first tackle #33120 (implement Spatial
> Reference System (SRS)) to avoid rework, but an implementer could
> confirm.
>
> Gates on `supports_transform` should be checked to see if they can use
> the new functionality safely, or if they should fallback to the old
> read/write SRID-0 behavior described in #27574.
>
> This is a blocker for fixing #27574, which is a pain point that has come
> up on the forum a couple times.

New description:

MySQL has an `ST_Transform` function since 8.0.13, and "all" Cartesian
transforms are
​[https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-32.html#:~:text=now%20supports%20all%20Cartesian%20projections
supported since 8.0.32], so we should add support for the `Transform` geo
function.

[https://dev.mysql.com/doc/refman/9.7/en/spatial-operator-functions.html
#function_st-transform docs]

It is likely that we should first tackle #33120 (implement Spatial
Reference System (SRS)) to avoid rework, but an implementer could confirm.

Gates on `supports_transform` should be checked to see if they can use the
new functionality safely, or if they should fallback to the old read/write

SRID-0 behavior described in #27464.

This is a blocker for fixing #27464, which is a pain point that has come

up on the forum a couple times.

--

--
Ticket URL: <https://code.djangoproject.com/ticket/37320#comment:1>