> Because of this MySQL change being backwards incompatible, it also broke restoring backups. No matter how you paint it, if MySQL isn't able to restore a back

> Because of this MySQL change being backwards incompatible, it also broke restoring backups. No matter how you paint it, if MySQL isn't able to restore a backup created with the backup utility of the same version, then this is MySQL's fault. It is absolutely not acceptable for a backup utility to run through but produce something that then cannot be restored. I would have expected mysqldump to blow up or even better, the newer daemon to not start up if it sees a schema that it doesn't support any more.