Rafael Mendonça França 4d1d7d3d1b Unify the logic to determine the default schema cache path for a database configuration ... When the application has more than one database configuration, only the primary was being loaded by default on boot time. All the other connection pools were loading the schema cache lazily. This logic can be found in: 351a8d9bc9/activerecord/lib/active_record/connection_adapters/pool_config.rb (L13) 351a8d9bc9/activerecord/lib/active_record/railtie.rb (L149-L178) The lazy code path wasn't using the same logic to determine the name of the default schema cache file that the Railties uses, so it was loading the schema cache of the primary config to all the other configs. If no table name coincided nothing bad would happen, but if table names coincided, the schema would be completly wrong in all non-primary connections.		2024-01-29 18:18:15 +00:00
..
dbs_test.rb	Fix Railties tests	2023-11-30 11:11:23 -05:00
framework_test.rb	Adding frozen_string_literal pragma to Railties.	2017-08-14 19:08:09 +02:00
log_test.rb	Revert "Avoid chdir error in Railties tests on Ruby master"	2020-12-26 15:01:24 +09:00
migrations_test.rb	Revert "Add config for validating migration timestamps"	2023-12-01 11:58:53 -05:00
multi_dbs_test.rb	Unify the logic to determine the default schema cache path for a database configuration	2024-01-29 18:18:15 +00:00
tmp_test.rb	rails tmp:clear: clear tmp/storage	2021-05-28 22:34:49 -04:00