#27064: Implement RenameIndex in a backwards compatible way -----------------------------+------------------------------------ Reporter: MarkusH | Owner: nobody Type: New feature | Status: new Component: Migrations | Version: master Severity: Normal | Resolution: Keywords: | Triage Stage: Accepted Has patch: 0 | Needs documentation: 1 Needs tests: 1 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -----------------------------+------------------------------------
Comment (by akki): Is there a reason why we cannot just simply deprecate `index_together`. My understanding is that the models file of the app will get modified from this {{{#!python class Meta: index_together = (('a', 'b')) }}} to this {{{#!python class Meta: indexes = [models.Index(fields=['a', 'b'])] }}} and everything should work fine (or not? Am I missing something?) I need some help to see where `RenameIndex` comes into picture here. -- Ticket URL: <https://code.djangoproject.com/ticket/27064#comment:4> 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 post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/065.f9b7faf9a6ceefc9b926f1f6ba9b0be1%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.