Clarify ActiveSupport::Cache::NullStore behavior [ci skip]

The caching guide currently indicates that values are not cached at all
when using ActiveSupport::Cache::NullStore.  However, values *are*
cached within the scope of a single web request.

This commit changes the guide to reflect that.

Closes #38638.
This commit is contained in:
Jonathan Hefner 2020-06-09 02:21:45 -05:00
parent b4bf143d6a
commit e8b5736531
1 changed files with 4 additions and 1 deletions

View File

@ -538,7 +538,7 @@ config.cache_store = :redis_cache_store, { url: cache_servers,
### ActiveSupport::Cache::NullStore
This cache store implementation is meant to be used only in development or test environments and it never stores anything. This can be very useful in development when you have code that interacts directly with `Rails.cache` but caching may interfere with being able to see the results of code changes. With this cache store, all `fetch` and `read` operations will result in a miss.
This cache store is scoped to each web request, and clears stored values at the end of a request. It is meant for use in development and test environments. It can be very useful when you have code that interacts directly with `Rails.cache` but caching interferes with seeing the results of code changes.
```ruby
config.cache_store = :null_store
@ -700,6 +700,9 @@ $ bin/rails dev:cache
Development mode is no longer being cached.
```
NOTE: By default, when development mode caching is *off*, Rails uses
[`ActiveSupport::Cache::NullStore`](#activesupport-cache-nullstore).
References
----------