I have recently had my db corrupted, and while I entirely blame this on our shoddy hosting (in the process of moving away) I was forced to work with my the db trying to restore it. I noticed that out of all the exp_ tables, seven of them were using the InnoDB storage engine, chiefly among them exp_comments, the absence/corruption of which also alerted me to a problem because without the control panel will not load (even though I have turned comments off and don’t use them anywhere on the site).
The tables are:
exp_comments
exp_comment_subscriptions
exp_pages_configuration
exp_rte_tools
exp_rte_toolsets
exp_update_log
exp_update_notices
Is that a recent change? Could I simply revert them back to MyISAM? If InnoDB support is required, shouldn’t it be mentioned on https://docs.expressionengine.com/latest/installation/requirements.html?
No engine requirements except for the cp_search_index
, which has to be MyISAM (for now).
Our default in the installer is MyISAM, but for some tables that are created later, such as comments or the update log we don’t specify an engine, so it will create one with the database default.
My guess would be that your host’s default is InnoDB. You’re safe with either 😊 .
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.