Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Can renaming a MySQL column be sped up by dropping indexes or foreign keys?
I need to rename one column in 170 tables in a MySQL database and its going really slow.
The columns all have an index plus a foreign key on them, would dropping the index/temporarily removing the foreign key speed up the process?
2 answers
You are accessing this answer with a direct link, so it's being shown above all other answers regardless of its score. You can return to the normal view.
I need to rename one column in 170 tables in a MySQL database and its going really slow.
[...]
Doesn't make much sense. A column name should be easy to rename and somewhat independent of the data the column stores.
Table data, index data, belong in physical ANSI-SPARC level, while entity names belong in the conceptual level.
[...]
The columns all have an index plus a foreign key on them, would dropping the index/temporarily removing the foreign key speed up the process?
Can you?
There might be other better alternatives to try... if you can, scaling the virtual machine up vertically for the task, and scaling it back down once the task is done, doesn't put the schema in a potential integrity compromise risk, while potentially coping with whatever CPU/Memory/IO bottleneck it might be having before scaling up.
I would simply turn off foreign key checks:
SET FOREIGN_KEY_CHECKS=0;
and make all the changes, and then turn foreign key checks back on:
SET FOREIGN_KEY_CHECKS=1;
0 comment threads
1 comment thread