Please list those widely used modern schema migration tools as they occur in other popular languages like PHP, Python, Perl, and so on.
In rails, users don't futz with migration version numbers. Those are handled automatically by the system. The user simply specifies a migration, e.g. "I want to add this column to this table." The migration is then automatically run when doing the next deployment. That doesn't work in 90% of the cases - it works in 100% of the cases.
Woe be unto the developer whose deployment process only works 90% of the time.
I already did in another comment but I'll repeat: django south, hibernate schemaupgrade, datamapper automigrate, postfacto (standalone python/postgres), sqlalchemy-migrate
e.g. "I want to add this column to this table."
The difference is that in Rails the user has to update the model and create a matching migration. In most other frameworks the second part is strictly optional and by default
implicit.
Woe be unto the developer whose deployment process only works 90% of the time.
That's not what happens. In practice there's always a review step.
At least several, maybe all, of those were directly inspired by rails migrations. Whether something automatic, but imperfect (renames, anyone?) is actually better than something explicit but easy enough seems a matter of taste.
Please list those widely used modern schema migration tools as they occur in other popular languages like PHP, Python, Perl, and so on.
In rails, users don't futz with migration version numbers. Those are handled automatically by the system. The user simply specifies a migration, e.g. "I want to add this column to this table." The migration is then automatically run when doing the next deployment. That doesn't work in 90% of the cases - it works in 100% of the cases.
Woe be unto the developer whose deployment process only works 90% of the time.