-
Notifications
You must be signed in to change notification settings - Fork 682
QuerydslPredicateBuilder
and QuerydslBindings
do not consider owning type
#2418
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
QuerydslBindings.getBindingForPath(…)
does not consider owning type
QuerydslBindings.getBindingForPath(…)
does not consider owning typeQuerydslPredicateBuilder
and QuerydslBindings
do not consider owning type
Note that the 1.13.x development line is end of life since August 2019. However, the issue persists also in the current version. The issue is related to both, |
mp911de
added a commit
that referenced
this issue
Jul 29, 2021
We now consider a qualified property path when registering and querying QuerydslBindings to ensure that paths matching various domain types do not accidentally get applied for a different type than they were registered for. Previously, a binding for Address.description would be also applied to User.description as only the property path description was considered when looking up bindings. Closes #2418
mp911de
added a commit
that referenced
this issue
Jul 29, 2021
We now consider a qualified property path when registering and querying `QuerydslBindings` to ensure that paths matching various domain types do not accidentally get applied for a different type than they were registered for. Previously, a binding for `Address.description` would be also applied to `User.description` as only the property path `description` was considered when looking up bindings. Closes #2418
christophstrobl
pushed a commit
that referenced
this issue
Sep 14, 2021
We now consider a qualified property path when registering and querying `QuerydslBindings` to ensure that paths matching various domain types do not accidentally get applied for a different type than they were registered for. Previously, a binding for `Address.description` would be also applied to `User.description` as only the property path `description` was considered when looking up bindings. Closes: #2418 Original Pull Request: #2422
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Spring data commons version : 1.13.23
I am currently maintaining an old project using Spring Boot 1.5.x .when I use
@QueryDSLPredicate
to bind query parameters, there is a problem with multiple different objects interfering with each other.during debug, i found
QuerydslPredicateBuilder.getPath()
method interal using cache.PropertyPathInformation
will compare thier path property , andPropertyPath.equals()
method not check owningType.so when i query by id params will hit wrong cache (their name and type is same).
I find same question in spring data jpa default controller(
RepositoryEntityController
)The text was updated successfully, but these errors were encountered: