Changing the related_name field causing pointless foreign key re-creations on MySQL migrations

[Thomas Aitken]

MySQL version = 8.0, Django version = 2.2.28. Each change to a related_name triggers a migration that looks like the following:
ALTER TABLE {table_name} DROP FOREIGN KEY {constraint_name};
ALTER TABLE {table_name} ADD CONSTRAINT {constraint_name} FOREIGN KEY ({other_table_id}) REFERENCES {other_table_name} (id);

In other words, it is pointlessly (?) dropping and creating the same foreign key constraint. Supposedly, this was fixed a long time ago for v2.1 (https://code.djangoproject.com/ticket/25253). But seems like, somehow, it's still present.

[Claude Paroz]

Django 2.2 is no longer supported. I didn't search the history, but have the strong feeling that this is solved in recent Django versions. Do you have the ability to test with more recent versions?