MyISAM engine error but the DB is all InnoDB

2018-10-12 19:41:53

On my install CiviCRM runs in a separate database that is entirely InnoDB, but Civi throws up the MyISAM engine error anyway. The rest of wordpress lives in a DB that is InnoDB by default, although the tables are a mix of the two types, but I don't see why that matters. So why am I getting the MyISAM Engine error in Civi?

Versions: CiviCRM 4.7.11, wordpress 4.6.1, PHP 5.6.24, MySQL 5.0.11

This issue was fixed in CiviCRM 4.7.12 with this commit: https://github.com/civicrm/civicrm-core/commit/2475b5509e9638fa2e9863256348c5415f362b72

Cheers,

Olivier;

I've seen this warning pop up a couple of times in the last month. My CiviCRM database is InnoDB but I notice Wordpress is MyISAM. Clearing Civi's cache clears the message. I believe Wordpress can be converted to InnoDB, so I will investigate that.

Wordpress 4.9.8, CiviCRM 5.6.0, MySQL 5.7.23, PHP 7.1.22

  • This issue was fixed in CiviCRM 4.7.12 with this commit: https://github.com/civicrm/civicrm-core/commit/2475b5509e9638fa2e9863256348c5415f362b72

    Cheers,

    Olivier;

    2018-10-12 19:59:34
  • I've seen this warning pop up a couple of times in the last month. My CiviCRM database is InnoDB but I notice Wordpress is MyISAM. Clearing Civi's cache clears the message. I believe Wordpress can be converted to InnoDB, so I will investigate that.

    Wordpress 4.9.8, CiviCRM 5.6.0, MySQL 5.7.23, PHP 7.1.22

    2018-10-12 20:15:13