Last modified: 2011-05-21 00:26:29 UTC
We live in new shiny 3rd millenium, yet MyISAM doesn't support transactions causing lulz like bug 28611; it's also more prone to corruption. To prevent users from making the mistake of choosing MyISAM, we should warn them sternly, just explaining it in help is not enough.
We have special code in the main classes for manually rollbacking changes in MyISAM (ugly! ugly!). But most of our codebase doesn't take caution for a transactionless db, so there are probably many places which could go wrong with MyISAM nowadays.
Created attachment 8561 [details]
Patch for this bug
Here's a patch to have the installer "scream bloody murder." I think it addresses the concerns raised.
-need-review+reviewed since mah would of checked it over before applying to trunk.
(In reply to comment #4)
> -need-review+reviewed since mah would of checked it over before applying to
and other people made follow-up commits for the things I missed.