You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ActiveRecord::Base.dump_schema_after_migration configuration setting is great for running migrations without errors in environments like Heroku that don't have pg_dump installed. Unfortunately it only applies to the db:migrate rake task. It would be great if it also applied to the db:migrate:up, db:migrate:down, db:forward, and db:rollback rake tasks so those tasks could be run without errors in Heroku.
The text was updated successfully, but these errors were encountered:
…igrate
Closes#20743.
The task `db:_dump` now only dumps the schema if
`ActiveRecord::Base.dump_schema_after_migration` is true. This has
effects:
- `db:migrate:up`
- `db:migrate:down`
- `db:forward`
- `db:rollback`
Conflicts:
activerecord/CHANGELOG.md
railties/test/application/rake/migrations_test.rb
The
ActiveRecord::Base.dump_schema_after_migration
configuration setting is great for running migrations without errors in environments like Heroku that don't havepg_dump
installed. Unfortunately it only applies to thedb:migrate
rake task. It would be great if it also applied to thedb:migrate:up
,db:migrate:down
,db:forward
, anddb:rollback
rake tasks so those tasks could be run without errors in Heroku.The text was updated successfully, but these errors were encountered: