Changes between Initial Version and Version 5 of Ticket #33120


Ignore:
Timestamp:
Sep 4, 2026, 9:22:24 AM (3 weeks ago)
Author:
Jacob Walls
Comment:

This work is a prerequisite for adding support for the Transform function (#37320), which is in turn a prerequisite for implementing an upgrade path to having GeoDjango able to read/write to SRID-aware columns in #27464.

We will need to be careful to not retain the has_spatialrefsys_table flag as a gate for whether to read/write SRID 0, because that work needs to be done in #27464.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #33120

    • Property Triage Stage Unreviewed → Accepted
    • Property Version 3.2 → dev
    • Property Owner nobody removed
    • Property Patch needs improvement set
    • Property Has patch set

  • Ticket #33120 – Description

    initial v5  
    11MySQL 8 introduced two new tables that allow the implementation of the `SpatialRefSys` and `GeometryColumns` models as well as related functions for adding new SRS entries to the database. Adding these two models and updating related functions to support them would be a good first step to improving GeoDjango's support for MySQL 8.
    22
    3 - Add `MySQLSpatialRefSys` model connecting to the `INFORMATION_SCHEMA.ST_GEOMETRY_COLUMNS` table (https://dev.mysql.com/doc/refman/8.0/en/information-schema-st-geometry-columns-table.html)
     3- Add `MySQLSpatialRefSys` model connecting to the `INFORMATION_SCHEMA.ST_SPATIAL_REFERENCE_SYSTEMS` table (https://dev.mysql.com/doc/refman/8.0/en/information-schema-st-spatial-reference-systems-table.html)
    44- Add `MySQLGeometryColumns` model connecting to the `INFORMATION_SCHEMA.ST_GEOMETRY_COLUMNS` table (https://dev.mysql.com/doc/refman/8.0/en/information-schema-st-geometry-columns-table.html)
    55- Enable `has_spatialrefsys_table` and `supports_add_srs_entry` backend features if MySQL version is greater than 8.0
Back to Top