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

Use Hibernates case-insensitive pattern matching when available. #165

Merged
merged 1 commit into from
Jan 24, 2025

Conversation

nstdio
Copy link
Collaborator

@nstdio nstdio commented Dec 11, 2024

This commit provides case-insensitive pattern matching when using =ilike= or =inotlike= that relies on Hibernate's implementation for ilike. However, if JPA provider is different from Hibernate we fallback to old implementation.

The reason behind this change is to allow Hibernate generate "proper" case-insensitive pattern matching query depending on database.

This commit provides case-insensitive pattern matching when using
`=ilike=` or `=inotlike=` that relies on Hibernate's implementation
for `ilike`. However, if JPA provider is different from Hibernate
we fallback to old implementation.

The reason behind this change is to allow Hibernate generate
"proper" case-insensitive pattern matching query depending on database.
@nstdio
Copy link
Collaborator Author

nstdio commented Jan 24, 2025

Friendly ping @perplexhub . Could you please take a look?

@perplexhub perplexhub merged commit 911eca6 into perplexhub:master Jan 24, 2025
1 check passed
@nstdio nstdio deleted the ilike-for-hibernate branch January 24, 2025 20:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants