We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In memory caches are themselves already cleared when you flush an environment, but should we also be clearing out our CacheKey records?
flush
CacheKey
It might provide a bit of a "clean state" mechanism for if/when things go wrong?
The text was updated successfully, but these errors were encountered:
I'm going with "no it shouldn't", at least for now.
I think there is value in having the DB records persisted through a flush, as it means that they do not need to be regenerated on the next page load.
Sorry, something went wrong.
No branches or pull requests
In memory caches are themselves already cleared when you
flush
an environment, but should we also be clearing out ourCacheKey
records?It might provide a bit of a "clean state" mechanism for if/when things go wrong?
The text was updated successfully, but these errors were encountered: