印象中MySQL有一个独有的 alter ignore add unique index的语法。
语法如下:
ALTER [ONLINE | OFFLINE] [IGNORE] TABLE tbl_name
行为类似于insert ignore,即遇到冲突的unique数据则直接抛弃而不报错。对于加唯一索引的情况来说就是建一张空表,然后加上唯一索引,将老数据用insert ignore语法插入到新表中,遇到冲突则抛弃数据。
文档中对于alter ignore的注释:详见:http://dev.mysql.com/doc/refman/5.1/en/alter-table.html
IGNORE
is a MySQL extension to standard SQL. It controls how ALTER TABLE
works if there are duplicates on unique keys in the new table or if warnings occur when strict mode is enabled. If IGNORE
is not specified, the copy is aborted and rolled back if duplicate-key errors occur. If IGNORE
is specified, only the first row is used of rows with duplicates on a unique key. The other conflicting rows are deleted. Incorrect values are truncated to the closest matching acceptable value.
然而在执行了 alter ignore table tableA add unique index idx_col1_u (col1) 后,还是报了以下错误:
#1062 - Duplicate entry '111' for key 'col1'.
不是会自动丢弃重复数据么?世界观被颠覆了。查了下资料原来是alter ignore的语法不支持innodb。
得知alter ignore的实现完全取决于存储引擎的内部实现,而不是server端强制的,具体描述如下:
For ALTER TABLE with the IGNORE keyword, IGNORE is now part of theinformation provided to the storage engine. It is up to the storageengine whether to use this when choosing between the in-place or copyalgorithm for altering the table. For InnoDB index operations, IGNORE is not used if the index is unique, so the copy algorithm is used
详见:http://bugs.mysql.com/bug.php?id=40344
当然解决这个问题的tricky的方法还是有的,也比较直白粗暴。具体如下:
ALTER TABLE tableA ENGINE MyISAM;
ALTER IGNORE TABLE tableA ADD UNIQUE INDEX idx_col1_u (col1)
ALTER TABLE table ENGINE InnoDB;
声明:本网页内容旨在传播知识,若有侵权等问题请及时与本网联系,我们将在第一时间删除处理。TEL:177 7030 7066 E-MAIL:11247931@qq.com