Fix embedded path ColumnInfo access for composite IDs (GH-2201) #2223
+82
−2
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.
Summary
Fix
IllegalArgumentException: Cannot obtain ColumnInfo for embedded pathwhen using class-based composite IDs as@Idproperties.Problem
When
ResolvingRelationalPropertyValueProviderresolves identifiers for entities with composite IDs, it delegates toDocumentValueProvider.getValue()for embedded paths.Embedded paths do not have a single
ColumnInfo, which results in anIllegalArgumentException.Solution
Update
DocumentValueProviderto properly handle embedded paths:getValue(): returnnullfor embedded paths (values are resolved via individual properties)hasValue()/hasNonEmptyValue(): recursively evaluate embedded propertiesChanges
MappingRelationalConverter.DocumentValueProviderto handle embedded paths correctlyResolvingRelationalPropertyValueProviderbehaviorTesting
All tests pass. Both class-based and record-based composite IDs are now handled correctly.
Fixes #2201
Checklist