feat: support contains operator for postgresql #3793
Merged
+722
−162
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.
What this PR changes/adds
Adds support for
contains
operator in SQL as it was done for in-memory store.Adds flexibility, defining a
SqlOperatorTranslator
interface that permits to specify how the operator is defined in the specific SQL implementation.Why it does that
stores feature consistence
Further notes
JsonFieldTranslator
is postgresql specific but it's located in thesql-core
, same for thePostgresOperatorTranslator
, maybe we should extract apostgresql
extension that takes care of registering common postgresql-related services, "refactoring never ends" :)validateOperator
from theSqlQueryStatement
constructor, because now that's implicit in theSqlOperatorTranslator
component: if the operator gets translated is valid, otherwise it's not.Linked Issue(s)
Closes #3736
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.