It's ridiculous. Sure dropping everything is an easy way to go but it shouldn't work like that.
Maybe flushdb functionality could be configurable?
How you can solve this (together with another organization problem):
1) Introduce a cache key prefix. It should be configurable but never empty. Default value: 'cache'.
2) Add the prefix to each key passed into get/set/del methods. It should be separated with the key by a colon ':' (e.g. 'cache:custom_cache_key').
3) Make reset method to delete all keys starting with the prefix.
nick4fake
commented
1 year ago
It's ridiculous. Sure dropping everything is an easy way to go but it shouldn't work like that. Maybe
flushdbfunctionality could be configurable?How you can solve this (together with another organization problem): 1) Introduce a cache key prefix. It should be configurable but never empty. Default value: 'cache'. 2) Add the prefix to each
keypassed intoget/set/delmethods. It should be separated with thekeyby a colon ':' (e.g. 'cache:custom_cache_key'). 3) Makeresetmethod to delete all keys starting with the prefix.