[DDC-3582] Wrong class is instantiated when using nested embeddables #1311
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.
Consider a nested embeddable hierarchy: Entity > Embeddable 1 > Embeddable 2. In this case, when fetching an entity from the database, Embeddable 1 will be instantiated as an instance of Embeddable 2.
This is because the wrong class name is passed as
embeddedClass
to the constructor ofReflectionEmbeddedProperty
from theClassMetadataInfo::wakeupReflection
method. This PR fixes this.