Migrations are fragile

[GoogleCodeExporter]

Migrations currently make assumptions that they shouldn't about the state
of the database. They should be rewritten to check the current status
before running, and check for success after running.

Original issue reported on code.google.com by ajlyon on 17 Jan 2010 at 8:05