If your mysql version is later than 5.6, then the default storage engine is InnoDB. After 5.6, the performance of InnoDB has been optimized very well, and MylSAM can basically be abandoned.
If it is a version before 5.6, you can consider @vus520's answer, because MylSAM does not support foreign key and transaction operations, and is only suitable for simple table relationships. InnoDB basically supports all situations.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
If you search online, you can refer to http://www.cnblogs.com/villion/archive/2009/07/09/1893762.html
Chado MylSAM
Write long InnoDB
Transaction strict InnoDB
In actual projects, we have all moved to InnoDB
If your mysql version is later than 5.6, then the default storage engine is InnoDB. After 5.6, the performance of InnoDB has been optimized very well, and MylSAM can basically be abandoned.
If it is a version before 5.6, you can consider @vus520's answer, because MylSAM does not support foreign key and transaction operations, and is only suitable for simple table relationships. InnoDB basically supports all situations.