印象中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