Update Projection section in reference documentation. #3449
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
For the time being we at least now document the current behaviour and how to cope with it. See: #3286
schauder
requested changes
Apr 26, 2024
|
|
||
| [NOTE] | ||
| ==== | ||
| Some JPA providers may require additional hints when working with <<projections.dtos,Class-based projections>> especially when using those directly with method derived queries. |
There was a problem hiding this comment.
That confuses me. @PersistenceCreator is a Spring Data annotation, I'm sure that JPA providers don't care about that.
I would expect that the situation is more: We need either a constructor taking all the properties as arguments and if it isn't the only constructor we need it to be marked with @PersistenceCreator.
There was a problem hiding this comment.
It's our code that determines input properties. We use our mechanism to discover whether there is a preferred constructor and the properties it takes.
| [NOTE] | ||
| ==== | ||
| Some JPA providers may require additional hints when working with <<projections.dtos,Class-based projections>> especially when using those directly with method derived queries. | ||
| If you are facing errors like `JpaSystemException: Specified result type did not match Query selection type` make sure to provide a constructor hint via `@PersistenceCreator` to be passed on, as outlined below: |
There was a problem hiding this comment.
It isn't so much outlined below but demonstrated, isn't it?
mp911de
force-pushed
the
main
branch
2 times, most recently
from
52ee55f to
61e6d36
Compare
mp911de
pushed a commit
that referenced
this pull request
Dec 3, 2024
For the time being we at least now document the current behaviour and how to cope with it. Closes: #3286 Original pull request: #3449
mp911de
added a commit
that referenced
this pull request
Dec 3, 2024
Tweak wording. See: #3286 Original pull request: #3449
mp911de
pushed a commit
that referenced
this pull request
Dec 3, 2024
For the time being we at least now document the current behaviour and how to cope with it. Closes: #3286 Original pull request: #3449
mp911de
added a commit
that referenced
this pull request
Dec 3, 2024
Tweak wording. See: #3286 Original pull request: #3449
mp911de
pushed a commit
that referenced
this pull request
Dec 3, 2024
For the time being we at least now document the current behaviour and how to cope with it. Closes: #3286 Original pull request: #3449
mp911de
added a commit
that referenced
this pull request
Dec 3, 2024
Tweak wording. See: #3286 Original pull request: #3449
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to: spring-projects/spring-data-commons#3216