Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Reduce cache bypasses - do not bypass custom metadata cache in setGroupTree #14292

Merged
merged 1 commit into from
May 25, 2019
Merged

Reduce cache bypasses - do not bypass custom metadata cache in setGroupTree #14292

merged 1 commit into from
May 25, 2019

Commits on May 23, 2019

  1. Reduce cache bypasses 

    We have been running this patch in production for some months. When you load up a contribution edit page
(for example) the custom data metadata is loaded without hitting the cache. This means that
unnecessary queries are done. The only reason to bypass the cache would be that it is stale
or parameter dependent. However, the staleness is/ should be dealt with when editing custom
fields & if it is not then there will be other impacts. The entity id is NOT passed into the part of
the code that goes into the cached value
    @eileenmcnaughton
    eileen authored and eileenmcnaughton committed May 23, 2019
    Configuration menu
    Copy the full SHA
    1203c8d View commit details
    Browse the repository at this point in the history