-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New "Handle Nested 'Order By's" Logic Leads To Hibernate QuerySyntaxExceptions Complaining About Seemingly Invalid Paths #2522
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
Comments
I've faced similar issue, in order to reproduce:
Code (redacted): Invalid query is being generated: |
Duplicate of #2496 |
Backported to |
Hey!
As we were updating from Spring Boot 2.6.6 to Spring Boot 2.6.7 in our Project, which subsequently leads to an update of Spring Data JPA from 2.6.3 to 2.6.4, our integration tests suddenly failed with the following exceptions:
After checking the changes introduced by updating from Hibernate 5.6.7 to 5.6.8 and further investigating what the now in Spring Boot 2.6.7 Spring Data BOM 2021.1.4 had in store, we stumpled upon a specific commit that was shipped with Spring Data JPA 2.6.4: c93aa25
Here logic was touched regarding nested order by handling. In our case this is not even a nested order by clause but still led to a regression which i could locally verify by shadowing the QueryUtils class with its 2.6.3 version which made the regression disappear.
This happens on
@Query
string queries in our project, where we also providePageable
s. For example:If need be i can see if i can create a mock project that reproduces this issue but unfortunately i have no time right now to investigate further.
This regression blocks us from updating to Spring Data JPA 2.6.3 to 2.6.4 and subsequently to keep track with the latest Spring Boot versions. We would appreciate if you can have a look at this issue, thank you very much!
If more information is required, please do not hestitate to contact me!
The text was updated successfully, but these errors were encountered: