-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Resolve handling of ESCAPE clause with LIKE queries on EclipseLink #2955
Labels
in: query-parser
Everything related to parsing JPQL or SQL
in: repository
Repositories abstraction
type: regression
A regression from a previous release
Milestone
Comments
gregturn
added
in: repository
Repositories abstraction
in: query-parser
Everything related to parsing JPQL or SQL
labels
May 15, 2023
Related: #2954 |
Looks like this is HSQL's fault. When I run the same tests against H2, it runs just fine. |
gregturn
added a commit
that referenced
this issue
May 17, 2023
Migrate tests to H2 to verify LIKE with ESCAPE works properly on EclipseLink with Spring Data JPA. See #2955
gregturn
added a commit
that referenced
this issue
May 17, 2023
Migrate tests to H2 to verify LIKE with ESCAPE works properly on EclipseLink with Spring Data JPA. See #2955
This fix should be candidate for backporting to supported versions of Spring Data JPA. |
mp911de
changed the title
Resolve handling of ESCAPE clause with LIKE queries on EclipseLink.
Resolve handling of ESCAPE clause with LIKE queries on EclipseLink
May 31, 2023
mp911de
added
type: bug
A general bug
type: regression
A regression from a previous release
and removed
type: bug
A general bug
labels
May 31, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
in: query-parser
Everything related to parsing JPQL or SQL
in: repository
Repositories abstraction
type: regression
A regression from a previous release
For some reason, EclipseLink doesn't handle the LIKE queries with SpEL expressions and the ESCAPE character. For Hibernate, this involved a change to the HQL grammer.
However for EclipseLink, this may be a different issue.
The text was updated successfully, but these errors were encountered: