I would like to ask what problems does mixed myISAM and InnoDB have in the deployment environment?

Yes. Using the Laravel framework, the data volume is myISAM. However, some partitions are referenced, and some InnoDB tables are automatically generated. So I want to ask: what is the problem with mixed use? What method does Laravel use to convert data into myISAM? Yes.

Using the Laravel framework, the data volume is myISAM.

However, some partitions are referenced, and some InnoDB tables are automatically generated.

So I want to ask:

1. What are the problems with such a mix?
2. What method does Laravel use to convert data into myISAM?

Reply content:

Yes.

Using the Laravel framework, the data volume is myISAM.

However, some partitions are referenced, and some InnoDB tables are automatically generated.

So I want to ask:

1. What are the problems with such a mix?
2. What method does Laravel use to convert data into myISAM?

1. It can be mixed. Because of the database design, you must consider your own needs and make appropriate choices for the table engine. It is normal to use multiple storage engines in a single database. The only thing you should note is that, when a transaction needs to operate both myisam and innodb, it is recommended that myisam operate before or after the transaction is completed.
2. It is not recommended to convert it. Maybe your databases use the features of innodb. If you confirm that the database does not use the features of innodb, consider turning it over.

Today, you don't have to worry about myisam and innodb,