Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: support contains operator for postgresql #3793

Merged
merged 1 commit into from
Jan 25, 2024

Conversation

ndr-brt
Copy link
Member

@ndr-brt ndr-brt commented Jan 23, 2024

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

  • I noticed that we have some things tangled between "sql" and "postgresql" specific, e.g. the JsonFieldTranslator is postgresql specific but it's located in the sql-core, same for the PostgresOperatorTranslator, maybe we should extract a postgresql extension that takes care of registering common postgresql-related services, "refactoring never ends" :)
  • removed the validateOperator from the SqlQueryStatement constructor, because now that's implicit in the SqlOperatorTranslator 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.

@ndr-brt ndr-brt merged commit de44b6f into eclipse-edc:main Jan 25, 2024
@ndr-brt ndr-brt deleted the 3736-final branch January 25, 2024 11:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

refactor: make TranslationMapping building whole SQL condition
2 participants