A solution to the wordpress annoyance?

So, back in the world of wordpress (like world of warcraft, but with much, much worse graphics), I was getting really sick of the whole “not able to save posts cleanly” thing. I mean … it worked, it was just really annoying.

So I did what I’ve done in the past: I smacked down a mysqldump of the important tables, dropped all the tables and did a clean install.

But then I had an idea!

MySQL has pluggable storage engines, right? And the default is MyISAM, right? Well, MyISAM sorta blows (doesn’t support transactions, is generally unsafe, uses ISAM indexing). So what if I were to take the table dump, and turn all those MyISAM tables into InnoDB tables….

See, I have already narrowed the problem down as far as “something wrong with one of the wordpress config tables” (as in, not something wrong with the php, and not something wrong with the post or comment tables on the mysql side). So … what could it be? Well, what if it’s that the options db is getting corrupted because of some glitch or another? And, further, what if said glitch is because MyISAM is a sloppy bastard that is moderately unreliable (which is generally true, it’s very much not an ACID compliant engine).

So I did that. Now my entire wordpress install is working off of InnoDB. Of course, I won’t know if that actually fixed the problem until the problem shows up again. But we’ll see, right?

Comments are closed.