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
At the moment, if one query is marked to be cached (by calling .cache()), the result can never be invalidated programatically, e.g. if data in the database was changed intentionally and the result of the query needs to change now, too. An invalidation method would be great to fix this problem.
The text was updated successfully, but these errors were encountered:
FlorianSW
added a commit
to FlorianSW/mongoose-cache
that referenced
this issue
May 1, 2017
At the moment, if one query is marked to be cached (by calling .cache()), the result can never be invalidated programatically, e.g. if data in the database was changed intentionally and the result of the query needs to change now, too. An invalidation method would be great to fix this problem.
The text was updated successfully, but these errors were encountered: