rails--rails/activerecord/test
Prathamesh Sonpatki 8b77d8e387
Fix prepared statements disabled test again
- Due to `assert_nothing_raised` this test was not really testing
  anything.
- So updated it to assert that the query gives expected result.
- Also in general we can use `connection.unprepared_statement` for
  testing queries w/o prepared statements but it can't be used in this
  case. This test cases was added because when prepared_statements
  config is set to false, then DetermineIfPreparableVisitor module
  does not extended by Arel visitor resulting into an error. Ref: https://github.com/rails/rails/pull/22748.
- Because DetermineIfPreparableVisitor module does not get added to the
  visitor chain only if prepared_statements is false while **setting up
  connection**, not when `unprepared_statement` is used.
- I have also added an assertion for making sure that prepared_config
  is set to false from the start, so that nobody accidentally removes
  the connection setup using `arunit_without_prepared_statements` and
  replaces it with stubs or unprepared_statement.
2016-11-20 14:20:35 +05:30
..
active_record/connection_adapters Add more rubocop rules about whitespaces 2016-10-29 01:17:49 -02:00
assets
cases Fix prepared statements disabled test again 2016-11-20 14:20:35 +05:30
fixtures Merge pull request #26466 from y-yagi/remove_duplicated_fixture_set_names 2016-09-13 13:21:28 -04:00
migrations modernizes hash syntax in activerecord 2016-08-06 19:37:57 +02:00
models Deprecate the behavior of AR::Dirty inside of after_(create|update|save) callbacks 2016-11-01 13:16:33 -04:00
schema Remove a confusing comment 2016-10-31 10:27:01 +09:00
support Fix typo s/with/without/ 2016-11-20 05:47:30 +09:00
.gitignore
config.example.yml Fix tests for prepared_statements: false and queries hitting `#select_all` 2016-11-19 21:52:52 +05:30
config.rb