Fix access of root property instead of child property #1775
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
When the child of a one-to-one relationship has an id, the value for that id gets read in the wrong way. We get the column name for that id use that to access the value in the RowDocument. This results in either no value at all being found or even worse, the value of a root entity with a property of same name being accessed. This is fixed by using the full AggregatePath instead of just the property for accessing that value. Closes #1684
schauder
force-pushed
the
issue/1684-converter-not-found
branch
from
6e4dd03 to
ea86ec7
Compare
mp911de
pushed a commit
that referenced
this pull request
Apr 22, 2024
When the child of a one-to-one relationship has an id, the value for that id gets read in the wrong way. We get the column name for that id use that to access the value in the RowDocument. This results in either no value at all being found or even worse, the value of a root entity with a property of same name being accessed. This is fixed by using the full AggregatePath instead of just the property for accessing that value. Closes #1684 Original pull request: #1775
mp911de
pushed a commit
that referenced
this pull request
Apr 22, 2024
When the child of a one-to-one relationship has an id, the value for that id gets read in the wrong way. We get the column name for that id use that to access the value in the RowDocument. This results in either no value at all being found or even worse, the value of a root entity with a property of same name being accessed. This is fixed by using the full AggregatePath instead of just the property for accessing that value. Closes #1684 Original pull request: #1775
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.
When the child of a one-to-one relationship has an id, the value for that id gets read in the wrong way.
We get the column name for that id use that to access the value in the RowDocument.
This results in either no value at all being found or even worse, the value of a root entity with a property of same name being accessed.
This is fixed by using the full AggregatePath instead of just the property for accessing that value.
Closes #1684