DBAL-1092: [GH-756] [DBAL-1062] Fix renaming indexes used by foreign key constraints

[doctrinebot]

Jira issue originally created by user @doctrinebot:

This issue is created automatically through a Github pull request on behalf of deeky666:

Url: #756

Message:

Platforms that do not support a SQL syntax for natively renaming indexes need to drop and recreate indexes to perform a rename.
Platforms like MySQL < 5.7 deny dropping indexes used by foreign key constraints. In this case foreign key constraints have to be dropped before dropping indexes and have to be recreated after the particular index(es) have been recreated.
This is a major issue right now for people trying to upgrade to DBAL 2.5.

[doctrinebot]

• relates to DBAL-1062: upgrade from v2.4.3 to v2.5.0 is forcing recreating Indexes making Doctrine unusable

[doctrinebot]

Comment created by @doctrinebot:

A related Github Pull-Request [GH-756] was assigned:
#756

[doctrinebot]

Comment created by @doctrinebot:

A related Github Pull-Request [GH-756] was closed:
#756

[doctrinebot]

Issue was closed with resolution "Fixed"

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.