You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yeah, that's way better. So the approach would be something like:
aiocache_disable_read: does not try to retrieve the value from the cache, but stores the result there
aiocache_disable_write: tries to read from cache first, if it's found returns it. In case it's not found, makes the original call, but does not save the result in the cache.
Then we wouldn't need the general aiocache_disable param, we could obtain the same behavior disabling both read and write.
Sometimes we want to disable the cache for specific calls to a decorated method.
Adding a keyword argument (like
aiocache_disable=True
) that is consumed by the decorators and disables the cache for that specific call.In this case, we don't try to load from the cache, but should we cache the result? My guess would be no, but interested in your thoughts around this.
The text was updated successfully, but these errors were encountered: