The only reason why Addictive Community still uses MyISAM as default storage engine has two words: FULLTEXT search. But since v5.6.4 (released in late-2011) MySQL supports FULLTEXT indexes for InnoDB tables. It's been five years, maybe it's a good time to finally get rid the old MyISAM as it was left behind since MySQL 5.5.
No work needs to be done on the source code, since the syntax remains exactly the same. But soon it will be possible to implement Transactional Statements (BEGIN and COMMIT) in operations that involve multiple tables, for example, creating or responding to a topic.
The only reason why Addictive Community still uses MyISAM as default storage engine has two words: FULLTEXT search. But since v5.6.4 (released in late-2011) MySQL supports FULLTEXT indexes for InnoDB tables. It's been five years, maybe it's a good time to finally get rid the old MyISAM as it was left behind since MySQL 5.5.
No work needs to be done on the source code, since the syntax remains exactly the same. But soon it will be possible to implement Transactional Statements (
BEGINandCOMMIT) in operations that involve multiple tables, for example, creating or responding to a topic.