-
Notifications
You must be signed in to change notification settings - Fork 1.5k
JPQL parser doesn't accept MOD(… , …)
#3277
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 guess the missing "SELECT b" at the front is the issue here. |
Thank you @vhbcm. Newer versions of data-jpa are more strict about jpql grammar which requires a |
@christophstrobl I tried. The
|
It seems the MOD function should be supported. I see it mentioned at least in https://docs.oracle.com/javaee/6/tutorial/doc/bnbuf.html |
MOD(… , …)
The samples used to validate MOD parsing in tests does not comply with the specification and falsely uses '/' instead of ',' as delimiter. Definition is: expression ::= MOD(arithmetic_expression, arithmetic_expression) See: https://eclipse.dev/eclipselink/api/4.0/eclipselink/org/eclipse/persistence/jpa/jpql/parser/ModExpression.html Closes #3277 Original pull request: #3280
We have tried to update Spring Data from 2022.0.12 to 2023.1.1. We are not using Hibernate, we use Eclipselink 4.0.2. The error is this:
The query:
The entire call stack:
The text was updated successfully, but these errors were encountered: