diff options
author | eileencodes <eileencodes@gmail.com> | 2019-06-03 15:58:22 -0400 |
---|---|---|
committer | eileencodes <eileencodes@gmail.com> | 2019-06-05 09:29:29 -0400 |
commit | 2f8b397258b66581409b0e6537f98ea9b56e9f19 (patch) | |
tree | 82150c33cad4d819089c7afb4eaf980be90727ea /activesupport/test/autoloading_fixtures/multiple_constant_file.rb | |
parent | 61c3ea8c048515fd2f1af30a7763c4aeddf7a5d6 (diff) | |
download | rails-2f8b397258b66581409b0e6537f98ea9b56e9f19.tar.gz rails-2f8b397258b66581409b0e6537f98ea9b56e9f19.tar.bz2 rails-2f8b397258b66581409b0e6537f98ea9b56e9f19.zip |
Treat ActiveRecord::Base and ApplicationRecord as "primary"
When someone has a multi-db application their `ApplicationRecord` will
look like:
```ruby
class ApplicationRecord < ActiveRecord::Base
self.abstract_class = true
connects_to database: { writing: :primary, reading: :replica }
end
```
This will cause us to open 2 connections to ActiveRecord::Base's
database when we actually only want 1. This is because Rails sees
`ApplicationRecord` and thinks it's a new connection, not the existing
`ActiveRecord::Base` connection because the
`connection_specification_name` is different.
This PR changes `ApplicationRecord` classes to consider themselves the
same as the "primary" connection.
Fixes #36382
Diffstat (limited to 'activesupport/test/autoloading_fixtures/multiple_constant_file.rb')
0 files changed, 0 insertions, 0 deletions