Fixed EntityGraphFactory overwriting subgraphs #2571
Closed
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.
EntityGraphFactory doesn't check whether a subgraph for a joined entity has already been created, and instead always creates a new one which overwrites the previous one.
E.g. when properties "a.b.field" and "a.c.field" are passed, it will first create a subgraph for "a" with a nested subgraph for "b", then create a new subgraph for "a" with a nested subgraph for "c", which will replace the the previous subgraph for "a". Therefore, no eager join for the b entity will be generated.
Related ticket #2527