Want to ask, what's the problem with mixing MyISAM and innodb in a deployment environment?

This is the way it is.

Using the Laravel framework, the repository is MyISAM.

But citing some of the repositories, the self-generated table of some INNODB structures.

So I want to ask:

1. What's the problem with this mix?
2. Laravel there any way to force the MyISAM?

Reply content:

This is the way it is.

Using the Laravel framework, the repository is MyISAM.

But citing some of the repositories, the self-generated table of some INNODB structures.

So I want to ask:

1. What's the problem with this mix?
2. Laravel there any way to force the MyISAM?

1, can be mixed, because the database design, it is necessary to consider their own needs of the table engine to make the appropriate choice, a library using multiple storage engines is normal, the only thing to note is that when the transaction needs to operate MyISAM and InnoDB, MyISAM it is best to operate before the transaction or after the transaction has completed.
2, not recommended to turn, perhaps you those libraries are using the InnoDB features, if you confirm that the library does not use the InnoDB feature, consider turning it.

To this day, do not think, MyISAM and InnoDB than no advantage,

