Wherein we write down some stuff that we know.
«
»

MySQL Hilarity

From the InnoDB backup section of the MySQL manual.

In addition to making binary backups as just described, you should also regularly make dumps of your tables with mysqldump. The reason for this is that a binary file might be corrupted without you noticing it. Dumped tables are stored into text files that are human-readable, so spotting table corruption becomes easier.

Ummmm, yeah…about that whole reading multi-megabyte text files to look for corrupted data…not gonna happen.

This entry was posted on Tuesday, January 2nd, 2007 at 4:28 pm and is filed under Databases. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.

One Response to “MySQL Hilarity”

  1. Peter D Says:
    January 3rd, 2007 at 2:46 pm

    Hey, why not just spell check the table dump to find the data corruption? That ought to solve the problem right there. Hmm, on second thought, MS Word thinks that MySQL should be either “Myself” or “Mosul”. Word 95 didn’t have the word “internet” in the dictionary, IIRC, so what we really need is a Nifty MySQL Data Table Dump Data Corruption Detector script. Got room in the 07 pipeline for that, WEBD?