Automatic REPAIR TABLE tablename after MySQL error 127

+1 sounds like a good idea.

Maybe a page like the upgrade page in the admin area which is shown on detection and allows the admin to run the repair.

+1 as a plugin (if that's possible when the DB throws a 127?) -1 as part of the core.

Wordpress is a blogging tool, not a sysadmin tool and therefore (by default) shouldn't pretend to be one.

Also, the 127 error happened/happens for a reason. You should find out why instead of just fixing the symptoms by doing a REPAIR TABLE.

You could do this with a plugin. You'll need to extend the $wpdb class to do it. I have not tested any of this, of course...

class my_wpdb extends wpdb {
	// override the print_error function
	function print_error($str = '') {
		if (mysql_errno($this->dbh) == 127 ) {
			// do REPAIR TABLE or whatever
		}
		else { 
			parent::print_error($str);
		}
	}

	// copy constructor to handle the annoying missing table variables problem
	function my_wpdb($old_wpdb) {
		// casting an object to an array returns the vars in the object
		// in the array.. so $vars['posts']='wp_posts'. Handy, no?
		$vars = (array)$old_wpdb;
		extract($vars, EXTR_OVERWRITE);
	}
}
// create a new object for the database
$my_wpdb = new my_wpdb($wpdb);

// assign it back to the main database
$wpdb = $my_wpdb;

That should work, I think. Should work in a plugin too. But of course, it won't work if you get the 127 error before the plugins get loaded.

Well, okay, so that extract($vars, EXTR_OVERWRITE); is wrong. Still, you could do it with a loop or something. Just need to make it get all of the variables set in the new object.

No Patch. Moved to 2.7

Is this going anywhere? There seems to be 50/50 support for plugin or core functionality.

The user-friendly part of me suggests that it might be a good idea to attempt a repair. The sysadmin in me says that user-level code should not be fiddling with sysadmin functions.

At the very least this should be a configurable option if it's brought in. (So that it could be turned off). I'd say off by default, but that would defeat the point in pretty much every case (I.E where a user isn't techy enough to do it themselves.)