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
Order by clause not created correctly if a manually defined query is not using an alias [DATAJPA-960] #1310
Comments
Oliver Drotbohm commented Would you mind adding a complete stack trace? Does actually turning this into a valid JPA query (i.e. |
arihan commented If I turn in
Full stackTrace:
|
arihan commented StackTrace:
|
arihan commented I found the solution, it works if the query is changed in "from Table t where t.name ..". However I think it should work in both cases. Better fix this issue |
Oliver Drotbohm commented The thing is, we have to start with a proper JPQL query in the first place. A query starting with |
Oliver Drotbohm commented I've just pushed a fix that improves the overall handling of queries that don't use an alias. Feel free to give the snapshots a spin. However, it's strongly recommended to start with a proper JPQL query in the first place |
arihan commented Thank you very much |
arihan opened DATAJPA-960 and commented
In my repository I have:
I am getting an error finishing with:
… order by where.name asc
Affects: 1.9.4 (Gosling SR4), 1.10.2 (Hopper SR2), 1.11 M1 (Ingalls)
Referenced from: commits 287104c, 9ce31b9, 890fd7f
Backported to: 1.10.3 (Hopper SR3), 1.9.5 (Gosling SR5)
The text was updated successfully, but these errors were encountered: