Ryuta Kamizono 9caa0cf57d Deprecate supports_statement_cache? ... `supports_statement_cache?` was introduced in 3.1.0.beta1 (104d0b2) for bind parameter substitution, but it is no longer used in 3.1.0.rc1 (73ff679). Originally it should respect `prepared_statements` rather than `supports_statement_cache?` (fd39847). One more thing, named `supports_statement_cache?` is pretty misreading. We have `StatementCache` and `StatementPool`. However, `supports_statement_cache?` doesn't mean `StatementCache`, but `StatementPool` unlike its name. https://github.com/rails/rails/blob/v5.1.0/activerecord/lib/active_record/statement_cache.rb https://github.com/rails/rails/blob/v5.1.0/activerecord/lib/active_record/connection_adapters/statement_pool.rb		2017-05-01 01:32:36 +09:00
..
active_record/connection_adapters	Add more rubocop rules about whitespaces	2016-10-29 01:17:49 -02:00
assets	Use YAML to serialize schema cache	2016-11-27 22:09:58 -05:00
cases	Deprecate supports_statement_cache?	2017-05-01 01:32:36 +09:00
fixtures	Correct spelling	2017-02-05 19:00:18 -06:00
migrations	modernizes hash syntax in activerecord	2016-08-06 19:37:57 +02:00
models	Remove useless test case	2017-04-26 22:41:32 +09:00
schema	Don't attempt to create a new record that was already created.	2017-04-20 19:45:58 -04:00
support	Handle non-existing $ARCONN	2017-02-27 08:23:02 -06: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