mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
45eb0f3bec
Previously if there were 2 migrations in one db and 1 migration in the other db all the migrations for db one would run and then all migrations for db two would run. If a migration in one database depended on a migration in another database then it could fail. This is probably pretty rare, however in a multi-db application that's moving tables from one db to another, running them out of order could result in a migration error. In this this change we collect all the versions for each migration and the corresponding db_config so we can run them in the order they are created rather than per-db. Closes #41664 Related #41538 Co-authored-by: John Crepezzi <john.crepezzi@gmail.com> Co-authored-by: Kiril Dokh <dsounded@gmail.com> |
||
|---|---|---|
| .. | ||
| application | ||
| command | ||
| commands | ||
| configuration | ||
| engine | ||
| fixtures | ||
| generators | ||
| isolation | ||
| minitest | ||
| railties | ||
| test_unit | ||
| abstract_unit.rb | ||
| app_loader_test.rb | ||
| backtrace_cleaner_test.rb | ||
| code_statistics_calculator_test.rb | ||
| code_statistics_test.rb | ||
| console_helpers.rb | ||
| engine_test.rb | ||
| env_helpers.rb | ||
| generators_test.rb | ||
| initializable_test.rb | ||
| json_params_parsing_test.rb | ||
| path_generation_test.rb | ||
| paths_test.rb | ||
| rack_logger_test.rb | ||
| rails_info_controller_test.rb | ||
| rails_info_test.rb | ||
| secrets_test.rb | ||
| version_test.rb | ||