-
Notifications
You must be signed in to change notification settings - Fork 132
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
IgnoreCase works only if a String property can be resolved to a column #518
Comments
Our Omitting that check seems to fix the issue. |
We now apply the UPPER function regardless of whether we could resolve the criteria property to a column. Previously, we required a resolved property of a String type which prevented non-mapped properties from case-insensitive queries. Closes #518
Reduce test method/class visibility. See #518
We now apply the UPPER function regardless of whether we could resolve the criteria property to a column. Previously, we required a resolved property of a String type which prevented non-mapped properties from case-insensitive queries. Closes #518
Reduce test method/class visibility. See #518
@mp911de thanks for the fix! |
Hello everyone, I'm sorry for writing an old issue, but I didn't want to create new one. |
Hello everyone,
I have the following select query using
R2dbcEntityTemplate
:When I run this, it produces the following query:
I would expect that
T_BOOK.TITLE
would also be wrapped with theUPPER()
function like the following:but it doesn't. In this case it does not produce real case-insensitive queries.
The text was updated successfully, but these errors were encountered: