MySQL db optimization and performance: 2 tables or 3 tables?

InnoDB is the state-of-the-art engine from MySQL and the default engine. Use it every time except you've good reasons to not use InnoDB in a special case Do not disfigure your table layout for performance reasons. There are most probably other ways to solve performace problems - when you ever get into one There are some reasons where I can think of where it makes sense, i.e.

If you need FULLTEXT-Index on some column which is only available with MyISAM engine. Here it can make sense to split a table to separate the column with needed FULLTEXT-Index.

InnoDB is the state-of-the-art engine from MySQL and the default engine. Use it every time except you've good reasons to not use InnoDB in a special case. Do not disfigure your table layout for performance reasons.

There are most probably other ways to solve performace problems - when you ever get into one ... There are some reasons where I can think of where it makes sense, i.e. If you need FULLTEXT-Index on some column which is only available with MyISAM engine. Here it can make sense to split a table to separate the column with needed FULLTEXT-Index.

Thank you. Does all the rest look fine in my tables? Thank you.

– Haradzieniec Nov 14 at 22:14 No, you should use InnoDB for both. For Fulltext Index I'll add a link. – Fatal Nov 14 at 22:46.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.