Open thanpolas opened 8 years ago
It's possible that this is actually an issue with cache-service-redis
. I'll need to do more digging, but cache-service
usually just passes through the data the children caches return. Also, redis is known to return OK
whereas cache-service
is not.
Actually, as currently written, .mset()
simply passes the provided callback to the last cache module's .mset()
implmentation. Modules [0] through [n-2] aren't passed a callback at all; those responses/errors are completely lost. Both .del()
and .flush()
are handled the same way. Conversely, .set()
passes the provided callback to the first cache module's .set()
implementation, and the responses from modules [1] through [n-1] are lost.
when executing an
mset()
with three key/value pairs, the response will be an array of 4 items withOK
.Using redis store, i'd expect to get 3 items