#35074: Altering spatial_index does not actually create/drop the index
----------------------------------------+------------------------
Reporter: Mário Falcão | Owner: nobody
Type: Bug | Status: new
Component: GIS | Version: 4.2
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
----------------------------------------+------------------------
Changing `spatial_index` on existing spatial fields causes migrations to
be generated as expected, but they do not actually drop/create the indexes
as desired when applied (`manage.py sqlmigrate` reports them as no-ops).
Detected on Django 4.2.8 with PostGIS, but also present on latest main
branch.
--
Ticket URL: <https://code.djangoproject.com/ticket/35074>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018cbbf16f00-ff8c114e-ee6b-4056-acc7-903e76a10a2b-000000%40eu-central-1.amazonses.com.
