December 13, 2013 in Classic self-hosted technical help
After upgrading MySQL I noticed that the default database engine is now INNODB, while my ipb installation is set so the original tables are all MyISAM.
Can I safely convert my MyISAM tables to INNODB? I understand that tables that use full text indexing cannot be converted to INNODB.
ipb supports both engines. But if you do change to innodb, make sure to update in your config file to change from myisam to innodb.
also, be sure you backup first.
thanks grumpy, good to know about the config file!
One thing I notice is that tables like ibf_blog_entries use fulltext indexing and so will not convert to innodb.... so can I have a mainly innodb set up with most tables being innodb, and keep myisam as the engine for fulltext indexed tables and still safely set innodb as the engine in the config file?
The act of setting to innodb in config turns off myisam only features such as fulltext search. So if you have a mix of both, setting it to innodb is safer as it won't run into errors as it tries to do full text search on that table. If you want full text search to be on, you should keep the setting as myisam.
Note that you are entering a territory that's not supported or fully tested. Any further, it's just what you try is the answer. I don't think any of us can give you a for-certain answer with mixed setups or guarantee that it'll continue to work after updates.
I have the configuration set to MyISAM and any table that supports or requires INNODB works perfectly. There is a huge difference if a couple tables are converted to INNODB and everything else is MyISAM.
This topic is now archived and is closed to further replies.
Started 7 hours ago
Started 12 hours ago
Started Saturday at 05:11 PM