Adds new JSON::Any criteria methods for querying jsonb columns#1015
Merged
Adds new JSON::Any criteria methods for querying jsonb columns#1015
Conversation
…ontain the ? character. Ref #197
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
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.
Ref #197
This PR adds in 3 new criteria method for
JSON::Anycolumnshas_keywhich performsWHERE jsonb ? 'some_key'.has_any_keyswhich performsWHERE jsonb ?| '{"this_key", "or_that_key"}'has_all_keyswhich performsWHERE jsonb ?& '{"this_key", "and_this_key"}'This makes doing queries on JSON columns a little easier since you can't do raw WHERE queries on these because they use the
?character which the PG shard uses as a placeholder refSide note: I'm not having this PR close the issue because I want to add 2 more in a separate PR to perform
@>and<@