Migration problems with mysql: Operation not allowed when innodb_forced_recovery > 0 [closed]

Commenting out the line innodb_force_recovery = 1 in /etc/my.cnf thus: # innodb_force_recovery = 1 made the mysql innodb tables in the database accessible. Apparently this setting causes innodb to become read-only. I hope this helps someone in the future. If you don’t have access to /etc/my.cnf on shared hosting, ask your host to fix it … Read more

If I consider changing my WordPress DB tables to InnoDB, will it have an effect on the way WordPress works?

There’s quite a lot of information on here about switching to InnoDB https://wordpress.stackexchange.com/search?q=innodb There are a number of things to think about: InnoDB is helpful with you’re faced with contention – ie when you have tables that are being written to as well as being read InnoDB does not support FULLTEXT indexes so plugins that … Read more

Large database causes slow load

DISCLAIMER : Not a WordPress Developer, Just a MySQL DBA There is a special table structure in Oracle called a Materialized View. Basically, it is built by performing a JOIN query (using no WHERE clause) and storing the result set. Then, simply SELECT from that static result set rather than rebuilding each JOIN result. First, … Read more

Can I explicitly specify ENGINE=InnoDB in WordPress?

If the code creating new tables uses dbDelta() (it should), you can filter the query (see wp-admin/includes/upgrade.php): add_filter( ‘dbdelta_create_queries’, function( Array $queries ) { foreach ( $queries as $table => $query ) { if ( FALSE !== stripos( $query, ‘CREATE TABLE’ ) ) { // change the query here } } return $queries; });