Issue #664 | Update handling nil value for PgHash #665
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
|
Thanks! ❤️ |
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.
Issue 664: Cache returns last value if nil value provided
When assigning attribute (which uses translations) nil value, it won't invalidate cache and will store previous value.
This possibly can affect any logic, but the common example is ActiveRecord validations. As cache uses previous value, it will pass presence validation, but it is incorrect as current value is nil.
Disabling cache for the attribute fixes situation, but actually it is not a solution.
This change appeared after version 1.2.9 and possibly after implementing logic for the Issue #535