MYISAM support
Permalink 1 user found helpful
Hello all.
Am I correct in assuming that after concrete5.6.x, there are no plans to reimplement MYISAM engine support?
If I use a hosting service that doesn't offer INNODB should I switch to a different CMS?
Thanks in advance.
Am I correct in assuming that after concrete5.6.x, there are no plans to reimplement MYISAM engine support?
If I use a hosting service that doesn't offer INNODB should I switch to a different CMS?
Thanks in advance.
Hi, you should either switch CMS or switch your hosting to something that allows innodb.
Unless things have changed (I could be wrong, if so - I apologise) but when you install 5.7 one of the pre-requisites is innodb.
Is the issue just that you want to stick to a particular host or that you don't want to use innodb?
Unless things have changed (I could be wrong, if so - I apologise) but when you install 5.7 one of the pre-requisites is innodb.
Is the issue just that you want to stick to a particular host or that you don't want to use innodb?
I was looking at free hosts, and a few don't offer INNODB.
Was just asking since changing ENGINE=INNODB to ENGINE=MYISAM no longer works.
Was just asking since changing ENGINE=INNODB to ENGINE=MYISAM no longer works.
I'm not sure how well you'll get on with 5.7 with free hosts. This version of concrete is a bit beefier and more demanding than previous versions.
However what I can tell you is that some tables in the 5.7 database (and also in 5.6) such as PageSearchIndex *cannot* be converted to InnoDB because they require FULLTEXT indexes, which are not supported by InnoDB and must therefore be MyISAM tables. On that basis I would think it unlikely that MyISAM support would vanish any time soon.