Since the question was reopened and closed again, let me take a moment to defend it and lay out why I believe it should be reopened as a legitimate question.
The main complaint is that it violates Gorilla vs. Shark. I do not believe this to be the case. Gorilla vs Shark lists 4 points about why this type of question is bad and violates the spirit of Stackoverflow. I agree with all the points listed and believe that my question does not fall victim to any of the 4 points listed.
Nobody needs to know the answer to this question
This question does need an answer. Knowing the difference between a MyISAM table and a InnoDB table is important. There are many differences between the two that a database developer does need to know. If foreign key constraints are a priority for your design, MyISAM is a bad choice. I only know this because of the answer. There are other differences that I know very little about, and would like further explanation, such as, row locking vs table locking. This is very important information to have when designing a database structure in MySQL, a widely used database back-end program.
It's not nearly specific enough
The question is very specific, it gets to heart of a database structure and two specific engines used in a specific database program. MySQL has its own engines, its own language (although based on SQL) and therefore has its own idiosyncrasies. This question is specific to only two of these engines, more open ended would be to ask what Engines are offered and what are the differences. This question only asks about the two most commonly used engines, one that was the default engine for years.
It is difficult to learn from these questions
This question is not difficult to learn from. A proper answer of the questions will explain the database engines and what they do (foreign key constraints, table locking vs row locking, others that i don't know about because the question can't currently be answered). I learned about foreign key constraints from the short answer that has been given. There is more to learn about the engines that is not opinion based, but it is fact based. This is impossible to learn by only reading the equivalent of case studies in the current stack overflow question database.
It drives away experts
I do not see why a serious MySQL expert would shy away from answering this question because it is based in fact, is poorly documented (my opinion) and many experts should be happy to show of their knowledge of the two most widely used database engines. This is an honest-to-goodness question that I face everyday in my work environment and I need to be able to make more well informed decisions. I don't think any MySQL expert would be appalled to see this question.
This is the criteria that is set forth in the FAQ on stack overflow and my question does not fall into the trap of Gorilla vs Shark. In my opinion it is more important to teach people how to fish rather than just giving them a fish. This is an example of that. I do not see why I should be asked to come on stackoverflow every time I need to design a database or table to ask specifically about that instance. However, if the difference between the two engines could be explained to me by an expert, than I can make informed decisions in the workplace without having to come to stackoverflow each time.