问题描述
我们正在尝试重命名 MySQL (5.1.31, InnoDB) 中作为另一个表的外键的列.
We're trying to rename a column in MySQL (5.1.31, InnoDB) that is a foreign key to another table.
起初，我们尝试使用 Django-South，但遇到了一个已知问题:
At first, we tried to use Django-South, but came up against a known issue:
http://south.aeracode.org/ticket/243
OperationalError: (1025, "将 './xxx/#sql-bf_4d' 重命名为 './xxx/cave_event' 时出错(errno: 150)")
OperationalError: (1025, "Error on rename of './xxx/#sql-bf_4d' to './xxx/cave_event' (errno: 150)")
和
将./xxx/#sql-bf_4b"重命名为./xxx/cave_event"时出错(错误号:150)
Error on rename of './xxx/#sql-bf_4b' to './xxx/cave_event' (errno: 150)
此错误 150 肯定与外键约束有关.参见例如
This error 150 definitely pertains to foreign key constraints. See e.g.
什么mysql error 1025 (HY000): Error on rename of './foo' (errorno: 150) 是什么意思?
http://www.xaprb.com/blog/2006/08/22/mysqls-error-1025-explained/
所以，现在我们尝试在原始 SQL 中进行重命名.看起来我们必须先删除外键，然后进行重命名，然后再次添加外键.听起来对吗?有没有更好的方法，因为这看起来很混乱和麻烦?
So, now we're trying to do the renaming in raw SQL. It looks like we're going to have to drop the foreign key first, then do the rename, and then add the foreign key back again. Does that sound right? Is there a better way, since this seems pretty confusing and cumbersome?
任何帮助将不胜感激！
推荐答案
AFAIK，删除约束，然后重命名，然后重新添加约束是唯一的方法.先备份！
AFAIK, dropping the constraint, then rename, then add the constraint back is the only way. Backup first!
这篇关于重命名 MySQL 中的外键列的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持跟版网！