Yves Senn 6d10d64cba fixture setup does not rely on AR::Base.configurations. ... As you can also configure your database connection using `ENV["DATABASE_URL"]`, the fixture setup can't reply on the `.configurations` Hash. As the fixtures are only loaded when ActiveRecord is actually used (`rails/test_help.rb`) it should be safe to drop the check for an existing configuration.		2013-06-15 14:58:38 +02:00
..
active_record/connection_adapters	Ensure disconnecting or reconnecting resets the transaction state	2012-09-15 00:03:04 +01:00
assets	Added test to illustrate bad binary blobs.	2012-01-31 13:45:00 -06:00
cases	fixture setup does not rely on AR::Base.configurations.	2013-06-15 14:58:38 +02:00
fixtures	has_many through obeys order on through association	2013-04-04 15:45:13 -04:00
migrations	Preserve magic comments and content encoding of copied migrations.	2013-03-09 15:38:02 +09:00
models	Ambiguous reflections are on :through relationships are no longer supported.	2013-06-13 09:46:42 -07:00
schema	Add test to AR's counter_cache_test.rb	2013-05-18 17:12:46 +09:00
support	Revert "Fix annoy warning, when executing testcase."	2012-11-30 12:07:55 +04:00
.gitignore	Refactor Active Record test connection setup. Please see the RUNNING_UNIT_TESTS file for details, but essentially you can now configure things in test/config.yml. You can also run tests directly via the command line, e.g. ruby path/to/test.rb (no rake needed, uses default db connection from test/config.yml). This will help us fix the CI by enabling us to isolate the different Rails versions to different databases.	2011-06-04 23:47:03 +01:00
config.example.yml	Simulated & actual (manual/skipped) PostgreSQL auto-reconnection tests.	2012-07-16 09:55:20 -07:00
config.rb