We also recommend the innoDB. wpForo always tries to create InnoDB tables, it depends on server MySQL version. Some version of MySQL doesn't support Full Text index for InnoDB so wpForo have to create MyISAM tables.
hello Robert. Thanks for answering. I doing a test in a new Mariadb environment 10.4.12 with galera cluster. But I was confused, because some WPforo tables were created as InnoDB and others as MyISAM. See attached image
how to solve this?
Yes, this is already changed in upcoming version. Those tables are not under the high processing, so they can be MyISAM. However, we decided to change to InnoDB even if it helps to improve performance for just 1%.
Yes, this is already changed in upcoming version. Those tables are not under the high processing, so they can be MyISAM. However, we decided to change to InnoDB even if it helps to improve performance for just 1%.
Not sure how you will do that in existing installations.
I tried to manually do that a while back but failed because of the MariaDB i used (10.1).
The errors were "error 1071 (key too long)".
That was solved in later versions of MariaDB but didn't tried again.
We'll not do that for update. It'll only be added for new installation.
No problem.
A BACKUP first (or two backups) and then manually:
https://kinsta.com/knowledgebase/convert-myisam-to-innodb/
great news @Robert 😀 Please don't forget to add this change to the changelog, as soon as I see it I will test it again.
thank you very much for understanding!
The change will not affect your database. The update process can't update your table engines. It's only for new installations.