-
Notifications
You must be signed in to change notification settings - Fork 359
AggregateReference with custom datatypes can not be converted to simple type #1828
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
type: bug
A general bug
Comments
I did some reproducing, debugging and testing here: #1829 |
#1194 feels somewhat related. |
schauder
added a commit
that referenced
this issue
May 23, 2025
Restructured reading conversion process into: - converting technology base types (JDBC Arrays). - standard and custom conversions. - module specific conversions (AggregateReference). Closes #1828
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Given following example with 2 entities: project and user, each having a custom datatype as id. User has a reference to project using
AggregatedReference<ProjectEntity, ProjectId>
. When Upgrading Spring Boot from 3.2.5 to 3.3.1, the application fails to create a user because theAggregatedReference
is not resolved to a simple type (creating a project works).During debugging I see that in Spring Boot 3.3.1
AggregatedReference<ProjectEntity, ProjectId>
is only converted to aProjectId
while in Spring Boot 3.2.5 the resultingProjectId
is further converted toUUID
byMappingRelationalConverter::getPotentiallyConvertedSimpleWrite
UserId
is identical):UserId
are identical):The text was updated successfully, but these errors were encountered: