Warn readers about false positive cache results #2500
Closed
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
|
Would it better to drive to solve this at the framework level so that it supports PhpRedis? |
|
I think I would rather try to solve this as mentioned above. |
|
Great, love hearing that! I'll submit a patch. |
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.
Using PhpRedis instead of Predis with Laravel’s default
RedisServiceProviderwill result in false-positive cache results across the framework, because PhpRedis returnsfalseinstead ofnullif a key does not exist.This PR warns the user about this unexpected behaviour and links to a drop-in replacement.