-
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
NEW as a part of a state field path expression in JPQL. #3128
Comments
Query works fine with the HQL parser. Looks like this is a JPQL parser issue. Can you confirm you are NOT using Hibernate? And if that is the case, what JPA provider are you using? |
We are not using Hibernate. We are using EclipseLink 4.0.2. |
Okay, |
A multi-node token that has NEW as one of its elements should work just fine in a JPQL query. See #3128
A multi-node token that has NEW as one of its elements should work just fine in a JPQL query. See #3128
A multi-node token that has NEW as one of its elements should work just fine in a JPQL query. See #3128
Merged to |
We have updated from 2022.0.6 to 2023.0.2 and we are getting BadJpqlGrammarException on the following query:
It does not seem to like the
j.creationTimestamp < :date
. The same query worked fine before the update.The tail of the exception trace:
The text was updated successfully, but these errors were encountered: