Added support for update an existing value not present in cache. #5
Conversation
This file contains 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
|
Will you resolve those conflicts? |
|
I updated my repo, everything seems ok (sorry I'm not used to this fork/pull/merge stuff) |
mthenw
added a commit
that referenced
this pull request
Sep 26, 2013
Added support for update an existing value not present in cache.
|
Thanks for this PR 👍 In few minutes there will be new version :) |
|
version 0.3.0 is in packagist |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Pull request for issue #4, replacing the
UPDATEorINSERTstatements regarding of the presence of the key in cache by a singleREPLACEstatement.Also updated tests so the case when a fresh
Storesets an existing key without having it in cache.