Thanks for clarifying that Mark. I've updated the ticket mentioning that we'll leave the resolution of the index name collision issue to your DEP.
On Monday, 1 December 2014 22:35:49 UTC, Marc Tamlyn wrote: > > I intend the new indexes to have customisable names, and to deconstruct > their name into the migration. This means that any changes in the name (if > the name is autogenerated) would be detected. It should be possible to do > renames. > > It is worth noting that mysql (and sqlite obviously) do not support > renaming of indexes and the index would need to be dropped and rebuilt. On > large tables this would be a problem, so we'll need some warnings in the > documentation about how to fix the index name so it is not identified as a > change. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/ab045baf-d57a-42cf-9b76-8596cb34d349%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
