Menu
The command rake db:migrate will apply all relevant new migrations to a database and will list in the output the migrations that were applied.
I'd like to know in advance what migrations will be applied so as to note down a list of the changes that are expected in a production environment.
Is there an option I can use in conjunction to rake db:migrate that will show me what changes will be applied without actually applying them?
580
A migration means that you move from the current version to a newer version (as is said in the first answer). Using rake db:migrate you can apply any new changes to your schema. But if you want to rollback to a previous migration you can use rake db:rollback to nullify your new changes if they are incorrectly defined.
rails_project theIV$ rake db:abort_if_pending_migrations (in /Users/theIV/Sites/rails_project/) You have 1 pending migrations: 20090828200602 Test Run "rake db:migrate" to update your database then try again. Show activity on this post. Show activity on this post. rake db:version will accomplish this on Rails 2.
Every time a migration is generated using the rails g migration command, Rails generates the migration file with a unique timestamp. The timestamp is in the format YYYYMMDDHHMMSS . Whenever a migration is run, Rails inserts the migration timestamp into an internal table schema_migrations .
You must rollback the migration (for example with bin/rails db:rollback ), edit your migration, and then run bin/rails db:migrate to run the corrected version.
Does rake db:migrate:status (rails 3+ only) fit the bill?
170
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
