feat: new array find operators #8766
Merged
+938
−27
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
…red directly to underlying driver (breaking)
…trings being JSON-stringified must be manually escpaed
This was referenced Mar 21, 2022
This was referenced Mar 22, 2022
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.
Added new find operators:
ArrayContainsArrayContainedByArrayOverlapBREAKING CHANGES:
JSON.stringify()tojson/jsonbcolumn types in Postgres. Instead, we delegate value directly to underlyingpgdriver. This is a correct way of handling jsons.array: truemust be explicitly defined for array json/jsonb valuesI should have included it in
0.3.0, but missed it. So, breaking change comes in0.3.1now.