mirror of https://github.com/rails/rails
009c7e7411
Right now adapters have to expose a rather byzantine API: - They must be defined in `active_record/connection_adapters/<name>_adapter` - They must define `ConnectionHandling.<name>_adapter_class` - They must define `ConnectionHandling.<name>_connection` All this is not very DRY and a bit annoying. Additionally it makes it very hard to define aliases (e.g. `mysql` => `trilogy`), or to substitute a default adapter for a specialized one. This refactor aims at making all this easier by exposing a simple `register` method, that third party adapters can call from a Railtie. |
||
|---|---|---|
| .. | ||
| bin | ||
| exe | ||
| lib | ||
| test | ||
| .gitignore | ||
| CHANGELOG.md | ||
| MIT-LICENSE | ||
| RDOC_MAIN.md | ||
| README.rdoc | ||
| Rakefile | ||
| railties.gemspec | ||
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/main/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