Opened 5 years ago

Last modified 13 hours ago

#33120 assigned New feature

Add OGC-compliant models for GeoDjango running on MySQL 8.0

Reported by: Jeff Hitchcock Owned by: Md. Saikat Islam
Component: GIS Version: dev
Severity: Normal Keywords: mysql
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by Jacob Walls)

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.

Change History (7)

comment:1 by Mariusz Felisiak, 5 years ago

Triage Stage: UnreviewedAccepted
Version: 3.2dev

Thanks for the report.

#27464 is probably a partially duplicate of this ticket. What do you think?

in reply to:  1 comment:2 by Jeff Hitchcock, 5 years ago

Replying to 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).

comment:3 by karthikeyaa-dev, 6 months ago

Owner: changed from nobody to karthikeyaa-dev
Status: newassigned

I'm working on this ticket.

comment:4 by Sachi Jain, 6 months ago

Patch needs improvement: set

in reply to:  description comment:5 by Jacob Walls, 3 weeks ago

Description: modified (diff)
Has patch: set
Owner: karthikeyaa-dev removed
Status: assignednew

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.

Last edited 3 weeks ago by Jacob Walls (previous) (diff)

comment:6 by Md. Saikat Islam, 2 weeks ago

Owner: set to Md. Saikat Islam
Patch needs improvement: unset
Status: newassigned

Since PR(https://github.com/django/django/pull/20923) is closed due to inactivity. I will be taking this from here.

comment:7 by blighj, 13 hours ago

Has patch: unset
Note: See TracTickets for help on using tickets.
Back to Top