- Notifications
You must be signed in to change notification settings - Fork 373
Supported nested conversions for AggregateReference. #2062
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left a few comments. I assumed this PR would had addressed the issue of late converter registration so that we can remove AggregateReferenceConverters
by considering AggregateReference
in writeValue
(and readValue
). We should revisit those converters for having a cleaner approach and to not distribute conversion of AggregateReference
to components outside of MappingRelationalConverter
/MappingJdbcConverter
.
...ain/java/org/springframework/data/relational/core/conversion/MappingRelationalConverter.java Outdated Show resolved Hide resolved
...data-jdbc/src/main/java/org/springframework/data/jdbc/core/convert/MappingJdbcConverter.java Show resolved Hide resolved
7ef8ac0
to fe66a43
Compare
I was able to simply remove |
Oops. |
...ain/java/org/springframework/data/relational/core/conversion/MappingRelationalConverter.java Outdated Show resolved Hide resolved
...g/springframework/data/jdbc/repository/JdbcRepositoryCrossAggregateHsqlIntegrationTests.java Outdated Show resolved Hide resolved
483808f
to ef1a0cb
Compare Ready for another round of review. |
That's merged and polished now. For the time being, I suggest keeping that change for 4.0 only and if it proves to not create downstream issues, we can consider it for backporting. |
Restructured reading conversion process into:
Closes #1828