Provide class for inspecting nested projections. #2420
Closed
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
spring-projects-issues
added
the
status: waiting-for-triage
meistermeier
force-pushed
the
issue/multilevel-projections
branch
from
cf8807d to
08ac9d0
Compare
|
Isn't a |
|
This is the problem with partially extracted and outdated documented things ( |
schauder
added a commit
to spring-projects/spring-data-jpa
that referenced
this pull request
Oct 26, 2021
…aph. When a property path based projection is specified we still return the root entity. But we do provide a fetchgraph. The JPA implementation will (should) load only the specified attributes eagerly. It most likely will also load all other attributes from all selected tables. Once we have infrastructure in place for for multilevel projections the same approach can and should be used for those. Currently this is not the case. Closes #2329 See spring-projects/spring-data-commons#2420
schauder
added a commit
to spring-projects/spring-data-jpa
that referenced
this pull request
Oct 27, 2021
…aph. When a property path based projection is specified we still return the root entity. But we do provide a fetchgraph. The JPA implementation will (should) load only the specified attributes eagerly. It most likely will also load all other attributes from all selected tables. Once we have infrastructure in place for for multilevel projections the same approach can and should be used for those. Currently this is not the case. See #2329 See spring-projects/spring-data-commons#2420
This was referenced Dec 1, 2021
mp911de
added
type: enhancement
christophstrobl
pushed a commit
that referenced
this pull request
Dec 13, 2021
Original Pull Request: #2420
christophstrobl
pushed a commit
that referenced
this pull request
Dec 13, 2021
Original Pull Request: #2420
christophstrobl
pushed a commit
that referenced
this pull request
Dec 13, 2021
Original Pull Request: #2420
christophstrobl
pushed a commit
that referenced
this pull request
Dec 13, 2021
Original Pull Request: #2420
christophstrobl
pushed a commit
that referenced
this pull request
Dec 13, 2021
Original Pull Request: #2420
christophstrobl
pushed a commit
that referenced
this pull request
Dec 13, 2021
Original Pull Request: #2420
christophstrobl
added a commit
that referenced
this pull request
Dec 13, 2021
Replace boolean flag with enum, assert open vs. closed projection and update javadoc. Original Pull Request: #2420
|
Thanks @meistermeier! Now available on main now. |
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.
As a result there will be a
Map<PropertyPath, Boolean>, indicating if the property path "ends" in an entity or not, that can get used as input for a selection/mapping filter in the dedicated store modules.Maybe it might makes sense to wrap the
Map<PropertyPath, Boolean>into an own class. For us it is sufficient right now to use the map.