database - Are there any reasons not to use Rails Migrations on production DB? -

database - Are there any reasons not to use Rails Migrations on production DB? -

the danger can think of developer using capistrano rollback migration on production database. there other risks can think of , what's best way avoid accidental migrations/database reset, etc?

edit: have daily backups in place. rephrase question way: there benefit in not using migrations @ (manual schema changes only)? , know rails teams doing it?

there potential info corruption/inconsistency, if modifying existing tables.

i'd recommend before doing migration or rollback ensure have date backup , if possible run migration on staging environment before rolling out production environment.

ruby-on-rails database migration rails-migrations