InnoDB and MyISAM

MyISAM: This is the default type, it is based on the traditional ISAM type, compared to other storage engines, MyISAM has most of the tools for checking and repairing tables, supports full-text search , is not transaction-safe, and does not support foreign keys , and if the rollback of a thing results in incomplete rollback and does not have atomicity, If executing a lot of select,myisam is a better choice.

InnoDB: This type is transaction-safe. It has the same characteristics as the BDB type, and they also support foreign keys. If you need a transaction-safe storage engine, it is recommended to use it. If your data performs a large number of inserts or update, for performance reasons, you should use the InnoDB table for performance reasons.

The LOAD table from master operation has no effect on InnoDB, and the workaround is to first change the InnoDB table to a MyISAM table, import the data and then change it to a InnoDB table, but not for tables that use additional InnoDB features (such as foreign keys)

Handwritten SQL CREATE TABLE:

CREATE TABLE News
(
ID int unsigned NOT NULL auto_increment,
Title varchar (+) NOT null default ' comment ' news headline ',
class_id int unsigned NOT NULL default ' 0 ' comment ' belongs to the category ID ',
Content text NOT null comment ' details ',
Primary key (ID),
Index ' I_title ' (title), index ' i_class_id ' (class_id)
) engine= ' innodb ' default charset UTF8 comment = ' news sheet ';

InnoDB and MyISAM