> I've lived in the world of Rails and Django so long, I sort of take schema migrations for granted. And there's lots more room for improvement over Rails and

> I've lived in the world of Rails and Django so long, I sort of take schema migrations for granted. And there's lots more room for improvement over Rails and Django migrations. Some of the problems: - Annoying version number management - Management of long "chain" of migration files - Unnecessary coupling between ORM and migration tool - Heavyweight process to generate and run each migration, which slows down local development - Bad testability Autosyncing local dev databases, and automatically generating migration scripts with a diff tool is a better approach, imho.