e7b1e118b9
This test was incorrect. `primary` was winning for the schema cache load but when you boot an application it's actually the first configuration that wins (in a multi db app). The test didn't catch this because I forgot to add a migrations_paths to the configuration. We updated the schema cache loader railtie as well because any application that didn't have a `primary` config would not be able to use the schema cache. Originally we thought we'd enforce a `primary` configuration but no longer feel that's correct. It's simpler to say that the first wins in a 3-tier rather than implementing a solution to require `primary` and / or allow aliases. Co-authored-by: John Crepezzi <john.crepezzi@gmail.com> Co-authored-by: John Hawthorn <john@hawthorn.email> |
||
|---|---|---|
| .. | ||
| bin | ||
| exe | ||
| lib | ||
| test | ||
| .gitignore | ||
| CHANGELOG.md | ||
| MIT-LICENSE | ||
| railties.gemspec | ||
| Rakefile | ||
| RDOC_MAIN.rdoc | ||
| README.rdoc | ||
= Railties -- Gluing the Engine to the Rails Railties is responsible for gluing all frameworks together. Overall, it: * handles the bootstrapping process for a Rails application; * manages the +rails+ command line interface; * and provides the Rails generators core. == Download The latest version of Railties can be installed with RubyGems: * gem install railties Source code can be downloaded as part of the Rails project on GitHub * https://github.com/rails/rails/tree/master/railties == License Railties is released under the MIT license: * https://opensource.org/licenses/MIT == Support API documentation is at * https://api.rubyonrails.org Bug reports can be filed for the Ruby on Rails project here: * https://github.com/rails/rails/issues Feature requests should be discussed on the rails-core mailing list here: * https://discuss.rubyonrails.org/c/rubyonrails-core