Supported nested conversions for AggregateReference.#2062
Supported nested conversions for AggregateReference.#2062
Conversation
mp911de
left a comment
There was a problem hiding this comment.
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.
7ef8ac0 to
fe66a43
Compare
I was able to simply remove |
|
Oops. |
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