[Django] #33120: Add OGC-compliant models for GeoDjango running on MySQL 8.0
Django
------------------------------------------+------------------------
Reporter: Jeff Hitchcock | Owner: nobody
Type: New feature | Status: new
Component: GIS | Version: 3.2
Severity: Normal | Keywords: mysql
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------+------------------------
MySQL 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.
- 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)
- 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)
- Enable `has_spatialrefsys_table` and `supports_add_srs_entry` backend
features if MySQL version is greater than 8.0
--
Ticket URL: <https://code.djangoproject.com/ticket/33120>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
Reporter: Jeff Hitchcock | Owner: nobody
Type: New feature | Status: new
Severity: Normal | Resolution:
Keywords: mysql | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by Mariusz Felisiak):
* version: 3.2 => dev
* stage: Unreviewed => Accepted
Comment:
Thanks for the report.
#27464 is probably a partially duplicate of this ticket. What do you
think?
--
Ticket URL: <https://code.djangoproject.com/ticket/33120#comment:1>
Django
Reporter: Jeff Hitchcock | Owner: nobody
Type: New feature | Status: new
Severity: Normal | Resolution:
Keywords: mysql | Triage Stage: Accepted
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Comment (by Jeff Hitchcock):
Replying to [comment:1 Mariusz Felisiak]:
> #27464 is probably a partially duplicate of this ticket. What do you
think?
They are definitely related, but that ticket has more to do with setting
SRID on columns (aka support for `ALTER TABLE _ ADD pt POINT SRID 4326`)
while this deals with being able to add new SRS entries into the database
(`MySQLSpatialRefSys` and `add_srs_entry`) and introspection of columns
that have spatial information (`MySQLGeometryColumns`).
--
Ticket URL: <https://code.djangoproject.com/ticket/33120#comment:2>
Django
Reporter: Jeff Hitchcock | Owner:
| karthikeyaa-dev
Type: New feature | Status: assigned
Severity: Normal | Resolution:
Keywords: mysql | Triage Stage: Accepted
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by karthikeyaa-dev):
* owner: nobody => karthikeyaa-dev
* status: new => assigned
Comment:
I'm working on this ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/33120#comment:3>
Django
Reporter: Jeff Hitchcock | Owner:
| karthikeyaa-dev
Type: New feature | Status: assigned
Component: GIS | Version: dev
Severity: Normal | Resolution:
Keywords: mysql | Triage Stage: Accepted
Changes (by Sachi Jain):
* needs_better_patch: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/33120#comment:4>