Opened 11 months ago
Last modified 2 months ago
#35074 closed Bug
Altering spatial_index does not actually create/drop the index — at Initial Version
| Reported by: | Mário Falcão | Owned by: | nobody |
|---|---|---|---|
| Component: | GIS | Version: | 4.2 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
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.
Note:
See TracTickets
for help on using tickets.