kotovalexarian-likes-github
/
rails--rails
mirror of https://github.com/rails/rails.git
1
0
Fork 0
Code Releases Activity

Merge pull request #39575 from jonathanhefner/clarify-null_store-behavior 

Clarify ActiveSupport::Cache::NullStore behavior [ci skip]
This commit is contained in:
Rafael França 2020-12-28 20:47:45 -05:00 committed by GitHub
parent 12a3ac1e08 e8b5736531
commit 947a9f903a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
guides/source/caching_with_rails.md
View File

@ -542,7 +542,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
@ -704,6 +704,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
----------