MySQL: diferentes motores para diferentes tablas

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?

preguntado el 10 de marzo de 12 a las 16:03

perhaps this post answers your query - stackoverflow.com/questions/5475283/… -

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

1 Respuestas

There is a penalty for mixing storage engines. Take a look aquí para más detalles.

respondido 10 mar '12, 19:03

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? - Aleksandar Vucetic

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

No es la respuesta que estás buscando? Examinar otras preguntas etiquetadas or haz tu propia pregunta.