Jira issue originally created by user @doctrinebot:
This issue is created automatically through a Github pull request on behalf of deeky666:
Currently renamed only indexes are scheduled for removal and recreation in the comparator. However recreating an index when only the name has changed is very inefficient on large tables as it internally requires a table recreation on most of the platforms. Many vendors offer a more efficient syntax for renaming indexes which saves the table recreation. This PR introduces this behaviour on capable platforms. Platforms that do not support this kind of syntax still use the current behaviour of dropping and recreating an index.
This PR also introduces the Table::renameIndex() method and the MySQL57Platform platform which adds support for explicitly renaming indexes.
Comment created by @doctrinebot:
A related Github Pull-Request [GH-473] was closed:
Comment created by @deeky666:
Fixed in commit: 6d0e8e2
Issue was closed with resolution "Fixed"