Merge pull request #15890 from w3lifer/patch-1

Cache Flushing as separate section
This commit is contained in:
Dmitry Naumenko
2018-03-13 18:11:15 +02:00
committed by GitHub

View File

@ -320,19 +320,6 @@ Since 2.0.14 you can use the following shortcuts:
User::find()->cache(7200)->all();
```
### Cache Flushing <span id="cache-flushing">
When you need to invalidate all the stored cache data, you can call [[yii\caching\Cache::flush()]].
You can flush the cache from the console by calling `yii cache/flush` as well.
- `yii cache`: lists the available caches in application
- `yii cache/flush cache1 cache2`: flushes the cache components `cache1`, `cache2` (you can pass multiple component
names separated with space)
- `yii cache/flush-all`: flushes all cache components in the application
> Info: Console application uses a separate configuration file by default. Ensure, that you have the same caching
components in your web and console application configs to reach the proper effect.
### Configurations <span id="query-caching-configs"></span>
@ -427,3 +414,17 @@ Some caching storage has size limitation. For example, memcache limits the maxim
of each entry to be 1MB. Therefore, if the size of a query result exceeds this limit,
the caching will fail.
## Cache Flushing <span id="cache-flushing">
When you need to invalidate all the stored cache data, you can call [[yii\caching\Cache::flush()]].
You can flush the cache from the console by calling `yii cache/flush` as well.
- `yii cache`: lists the available caches in application
- `yii cache/flush cache1 cache2`: flushes the cache components `cache1`, `cache2` (you can pass multiple component
names separated with space)
- `yii cache/flush-all`: flushes all cache components in the application
> Info: Console application uses a separate configuration file by default. Ensure, that you have the same caching
components in your web and console application configs to reach the proper effect.