Dear nerdworld

Is there any way to convert a sizable MySQL database containing this blog to sqlite? Here are some of the ways that don’t work:

  1. Using the mt-db-convert.cgi script: this ought to work, but is killed by the reaper at Pair. After exchanging around ten emails with the genuinely helpful and friendly support there, and then spending half an hour on the phone to Pittsburgh, we established that even when the scipt runs to a conclusion, it crashes with incomprehensible error messages.
  2. Using MySQLdump to get a listing of the database and then reading that into the SQLite database browser, which is supposed to understand this things. It claims there is “an error at line 2013051320”. There is, of course, no such line.
  3. Using the SQL-Fairy set of Perl modules. They come highly recommended, take no more than half a day to install on a fast machine. Feed them a 6MB SQL file and they die at line 18, the first one that starts “CREATE TABLE“, protesting that it does not start with “create”.
  4. I have not yet tried finding the authors of all or any of these programs; cutting their throats over my keyboard and then typing fast while my fingers splash in hot blood, but as soon as I get the chance, I will. I’m pretty certain that no lesser sacrifice will work.

In the meantime, if you find your comment won’t post, I apologise. I have done my best.

This entry was posted in nördig. Bookmark the permalink.

One Response to Dear nerdworld

  1. My blog runs on Pair as well, WordPress, not MT, but using PHP and MySQL. I don’t have enough readers (or comments) to have any useful feedback on comment-posting problems, but recently I’ve noticed some 500 errors when I post my own stuff. Not consistently, but often enough. The post always seems to get posted, though.

    This might be associated with my starting to use Pair’s PHP wrapper, which allows WordPress’s PHP code to run as me rather than as ‘nobody’, which in turn lets me use safer permissions on some of my directories (so I’m not about to go back).

    I haven’t been able to find anything useful in my logs when this happens, either, nor has Pair support; also odd, and no doubt a clue that I’m not able to read.

    Consider running mt-db-convert from a non-Pair host.

    Saving the best for last, Google Translate has a Japanese-to-English beta. Pretty amazing, all things considered.

    http://64.233.179.104/translate_c?hl=en&langpair=ja%7Cen&u=http://as-is.net/wiki/MT_Database_Converter/ja

    http://www.google.com/translate_t

Comments are closed.