Enable clear_cache to be called#15
Open
mephillips-durham wants to merge 1 commit intowragge:masterfrom
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I was using omeka_s_tools to create a bunch of linked resources. For example, I might need to create an object and link it to a person. As the person might already exist, I was searching for the person, and if not found, creating it. If a later object linked to the same person, the newly-created person was not found because the search API call was cached. So I wanted to use clear_cache after creating a person to avoid this problem. Unfortunately the clear_cache routine had a bug and cannot be called in its current form. This is a simple fix to allow clear_cache() to be used, but the use of the cache could still trip people up if they are doing a mixture of creating and searching.