This entry was published at least two years ago (originally posted on January 14, 2003). Since that time the information may have become outdated or my beliefs may have changed (in general, assume a more open and liberal current viewpoint). A fuller disclaimer is available.
After struggling with things for a few hours tonight, I’ve managed to succesfully convert the database backend for MovableType to MySQL.
What does this mean? Well…good question. For you, the end-user, not much, though as MySQL is supposed to be a bit faster, posting comments might be a bit more responsive than it was before. For me as the author/administrator, it should mean a bit more speed when creating/editing entries, and a lot more options as far as what I can do on a design/implementation level.
At least, that’s the theory. If nothing else, according to one of the moderators of the MovableType Support Forums, “If you have the choice, pick mysql. :) A little faster, more stable, easy to browse the database….” Good enough for me!