Allow data dump connection to be configured lewhit
Add primary key to data_migrations table aandis
Add abort_if_pending_migrations
rake tasks tomgia
Add rake data:schema:load
timkrins
Fixing rake db:schema:load:with_data
for Rails 6
Note:
Rails 5.0 is no longer maintained. The gem will still work but it is not being actively tested.
Fixing needs_migration?
method for Rails 5.2 and up EnomaDebby
Fix rolling back schema migrations failing for Rails 5.2 and above
Compatiblity with Rails 6 RC2 y-yagi
Fix migrations being generated in wrong folder
Support for Rails 6 No longer supporting Rails 4.2
Ruby 2.2 and 2.3 are no longer actively validated with tests since they are both EOL
Fix capistrano migration tasks to only skip migrations if there are no changes in the db/data and db/migrate folders
Change database task to use data_migrations_path_configuration
Add support to configure data migration path
Fixes to db:schema:load:with_data
+ db:structure:load:with_data
definition, thanks to craineum
Remove support for legacy migrations (from v2).
IMPORTANT: If you used this gem from before version 2, make sure to run migration script
DataMigrate::LegacyMigrator.new.migrate
Failure to do so may cause re-running old migrations
Support for Rails 5.2 Deprecated support for Rails 4.1 Internal changes to make data-migrate behavior more similar to Rails migrations
Deprecated support for rails 4.0 Improvements to timestamped migrations, thanks to Pierre-Michard
rake data:migrate:status
to return result in chronological order
Regression fix, thanks to subakva
The concept of schema:dump to data migrations, thanks to tobyndockerill
data_migrate table into rails schema dump, thanks to jturkel
- Add support for Rails 5.1
- No longer testing EOL rubies
Rails 5.0 support thanks to jturkel and abreckner
(gacha) Capistrano fixes
--skip-schema-migration
removed deprecated. This gem will no longer generate schema
migrations. It still supports running schema/data migrations with one command.
(bilby91) Capistrano support
User Rails.application.config.paths["db/migrate"]
instead of hard coded
path to db migrations