#30867: Old indexes should be dropped after new ones are created. -------------------------------------+------------------------------------- Reporter: Simon Charette | Owner: nobody Type: | Status: new Cleanup/optimization | Component: Migrations | Version: master Severity: Normal | Resolution: Keywords: | Triage Stage: | Unreviewed Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+-------------------------------------
Comment (by Claude Paroz): > Is there any reason except for double index storage needs not to do it? No, if we can reasonably estimate that the risk of introducing regressions is low and that it doesn't add too much code complexity. -- Ticket URL: <https://code.djangoproject.com/ticket/30867#comment:3> 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 django-updates+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/067.ec7b8178bba4549ce413abac1a937ccc%40djangoproject.com.