MySQL - Different Engines for Different Tables

Question

MySQL allows you to specify a different engine for a table from the server default engine. What kind of overhead does that create though? If I wanted to join a table that uses InnoDB with a table that uses MyISAM, which engine does MySQL use to run queries on that resulting temp table? For example, if I wanted to perform a task on that resulting temp table that only one engine can do (such as full text indexing), will the MySQL optimizer know to apply the right engine?

Is there any other reason not to specify particular engines for particular tables, even if they might differ from the server default?

Villenage

perhaps this post answers your query - #5475783 – Paleozoic

Unless you have specific reasons for mixing storage engines (e.g. proven performance problems), just avoid it. – Tatia

Answer 1

There is a penalty for mixing storage engines. Take a look here for details.

Inartificial

word "here" is a link towards mysqlperformanceblog. I always take them quite competent, so didn't search for more links. Did you mean some more links? – Inartificial

Ha, sorry, I read it first on my mobile which apparently did not seem to dump out a link. Cheers, – Devondevona