diff options
author | Jeremy Wadsack <jeremy.wadsack@gmail.com> | 2015-06-28 15:11:34 -0700 |
---|---|---|
committer | Jeremy Wadsack <jeremy.wadsack@gmail.com> | 2016-07-12 23:35:29 -0700 |
commit | 31a8588a01cf5aadb864f609efad6ee24b5d4055 (patch) | |
tree | 6d5929b7d83782b51650c0a548362656b2c11f84 /activerecord/test/cases/test_case.rb | |
parent | fc50f1fd50b05dc7e0f259dbe840e6d292e85aef (diff) | |
download | rails-31a8588a01cf5aadb864f609efad6ee24b5d4055.tar.gz rails-31a8588a01cf5aadb864f609efad6ee24b5d4055.tar.bz2 rails-31a8588a01cf5aadb864f609efad6ee24b5d4055.zip |
Create connection.active_record notification and use that to ensure that lazy-
loaded model classes have their connections wrapped in transactions.
See #17776
In Rails 4 config.eager_load was changed to false in the test environment. This
means that model classes that connect to alternate databases with
establish_connection are not loaded at start up. If use_transactional_fixtures
is enabled, transactions are wrapped around the connections that have been
established only at the start of the test suite. So model classes loaded later
don't have transactions causing data created in the alternate database not to
be removed.
This change resolves that by creating a new connection.active_record
notification that gets fired whenever a connection is established. I then added
a subscriber after we set up transactions in the test environment to listen for
additional connections and wrap those in transactions as well.
Diffstat (limited to 'activerecord/test/cases/test_case.rb')
0 files changed, 0 insertions, 0 deletions