Add warning about skipped conditions #352
Merged
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
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.
The issue - both
QueryandScanoperations support only one condition for an attribute. Actually they support more than one Dynamoid uses deprecated optionsQueryFilterandScanFilterto specify conditions and they don't support.So here I added warning messages when user mistakenly specifies several conditions for the one field in the
wheremethod and only the last condition wins - other are ignored.Following cases are handled:
where('age.gt': 10, 'age.lt': 20)where('age.gt': 10).where('age.lt': 2)The warning message looks like:
Where conditions may contain only one condition for an attribute. Following conditions are ignored: {:"age.gt"=>2}`