While yours seems ok, personally i have set all WP tables to InnoDB.
Some say that for some types of tables old isam is faster. But in 2023 i don't think so.
https://blogs.oracle.com/mysql/post/still-using-myisam-it-is-time-to-switch-to-innodb
Hi @dimalifragis,
While yours seems ok, personally i have set all WP tables to InnoDB
Well, in this post by @robert
https://wpforo.com/community/postid/11391/
On: 08/10/2017
... he recommends the following tables as innoDB
- wp_wpforo_forums (mine is MyISAM)
- wp_wpforo_posts (mine is MyISAM)
- wp_wpforo_topics (mine is MyISAM)
- wp_wpforo_profiles (mine is MyISAM)
- wp_wpforo_views (mine is already InnoDB)
... and
'And make sure the following tables Engines are still MyISAM:'
- wp_wpforo_likes (in ver. 2.2.3 = reactions) (mine is InnoDB)
- wp_wpforo_visits (mine is InnoDB)
So, I don't know if I should keep them this way.
I wonder what's recommended by the developers for wpForo 2.2.3
I'm working with MySQL Version 5.7.44-log-cll-lve
Would you still recommend switching to innoDB?
Thx for the link @dimalifragis
Hi @jorgew,
It's better to set all tables as InnoDB, you ken keep _reactions as MyISAM. All changes should be done in phpMyAdmin database manager. We recommend backup the database before any manipulation.
