Add a functional test covering #8127#10388
Closed
mpdude wants to merge 2 commits intodoctrine:2.14.xfrom
Closed
Conversation
This was referenced Jan 12, 2023
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Before merging, let's wait what conclusions #10411 or #10389 make.
This PR adds a functional test covering the use case reported in #8127.
It uses joined table inheritance across a hierarchy of three entity classes, with the root and middle class even being abstract entity classes. All three classes contain a mapped field.
As long as all three entity classes are declared in the Discriminator Map, the leaf (concrete entity) class can be queried through either the root or leaf class name, and all fields will be initialized correctly.
When the middle class is not included in the DM, its fields will not be queried and the entity is not hydrated correctly.
When the middle class is not an
@Entityclass, but an abstract@MappedSuperclass, it need not be included in the DM for things to work.