Core: MyISAM on posts table

[luceos]

I'm not sure, but I noticed that the posts table has MyISAM, the others have correctly InnoDB.

[luceos]

Seems this was a decision. Any reason why?

[franzliedke]

Probably because of that FULLTEXT index right below that line.

[luceos]

I'm not sure that requires myisam.. Right?

Edit, this explains it better.

And additional comparison: http://stackoverflow.com/a/15678615/717181

We internally never suggest MyISAM, that's why I got interested.

[franzliedke]

Not in MySQL 5.5, though. That's what we support...

[matteocontrini]

Hi everyone, any chance you could reconsider the decision of using MyISAM for the posts table? I'm not sure how much this will affect users, but maybe MySQL 5.5 support could be dropped. Since the release of MySQL 5.6, the FULLTEXT index is supported by InnoDB as well.

The fact that there's a MyISAM table among InnoDB table is causing me some headaches here because most backup solutions (including mysqldump) work best with InnoDB, and that MyISAM table is creating some troubles for achieving point-in-time backups.

Thank you.

[tobyzerner]

@matteocontrini Yep in beta 8 the posts table will be converted to InnoDB. No more MyISAM 🎉