Table conversion storage engine method summary _ MySQL

Summary of the table conversion storage engine method bitsCN.com
Note: After the storage engine is modified, the proprietary features of the original storage engine will be lost. For example, if an InnoDB is converted to the MyISAM storage engine and then returned, the foreign keys originally defined in the original InnoDB will be lost. Method 1: alter table [SQL] mysql> ALTER TABLE mytable ENGINE = InnoDB; the easiest way to replace a TABLE from one storage ENGINE with another storage ENGINE is the ALTER TABLE command. Features: a. suitable for all storage engines. B. The conversion process takes a lot of time. C. the Source table will be read and locked during conversion. Method 2: Dump and Import use mysqldump to export data tables and modify the create talbe statement of the Dump file. Modify: a. delete the drop talbe statement in the dump file to prevent loss of source data when the dump fails. B. modify the table name. The database definitely does not allow the same table name to appear, even if the storage engine is different. C. modify the storage engine. Methods-3, CREATE, and SELECT have a balance between the speed of method-1 and the security of Method-2. Create a table and use the INSERT... SELECT statement of mysql to transfer data. [SQL] mysql> CREATE TABLE innodb_table LIKE myisam_table; mysql> ALTER TABLE innodb_table ENGINE = InnoDB; mysql> INSERT INTO innodb_table SELECT * FROM myisam_table;
BitsCN.com