5 ms·
Please list I already did in another comment but I'll repeat: django south, hibernate schemaupgrade, datamapper automigrate, postfacto (standalone python/postg
by moe 16y ago
Please list
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.
However, I've already been accused of strawmanning, so rather than taking this further offtopic
let me just point you to http://south.aeracode.org/docs/tutorial/part1.html http://south.aeracode.org/docs/tutorial/part1.html
- kemiller 16y agoAt 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.
- moe 16y agoAt least several, maybe all, of those were directly inspired by rails migrations. Actually most of them (except datamapper and postfacto) have existed before rails was created. And I'll argue strongly against "matter of taste" when it comes to error-prone routine procedures.