-
Notifications
You must be signed in to change notification settings - Fork 132
SpEL parsing does not consider multiple usages and nested object references #373
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
Good catch, we need to fix this bug. |
mp911de
added a commit
that referenced
this issue
May 27, 2020
We now use SpelQueryContext and SpelExtractor for analysis and rewrite of queries using SpEL.
mp911de
added a commit
that referenced
this issue
Jul 20, 2020
mp911de
added a commit
that referenced
this issue
Jul 20, 2020
This commit deprecates API that has been moved to Spring R2DBC.
mp911de
added a commit
that referenced
this issue
Jul 21, 2020
We now use Spring R2DBC DatabaseClient and utilities to implement Spring Data R2DBC functionality.
schauder
pushed a commit
that referenced
this issue
Jul 22, 2020
We now use SpelQueryContext and SpelExtractor for analysis and rewrite of queries using SpEL. Original pull request: #376.
schauder
added a commit
that referenced
this issue
Jul 22, 2020
Using soft assertions for more expressive test failures. Original pull request: #376.
schauder
pushed a commit
that referenced
this issue
Jul 22, 2020
We now use SpelQueryContext and SpelExtractor for analysis and rewrite of queries using SpEL. Original pull request: #376.
schauder
added a commit
that referenced
this issue
Jul 22, 2020
Using soft assertions for more expressive test failures. Original pull request: #376.
This is fixed. |
mp911de
added a commit
that referenced
this issue
Jul 23, 2020
This commit deprecates API that has been moved to Spring R2DBC.
mp911de
added a commit
that referenced
this issue
Jul 23, 2020
We now use Spring R2DBC DatabaseClient and utilities to implement Spring Data R2DBC functionality.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A
@Query
with multiple parameters evaluated bySPeL
doesn't workException:
After some debugging, looks like parses evaluates only one expression:
The text was updated successfully, but these errors were encountered: