You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You are right, this is a regression. We migrated row reading into an intermediate type so that applications no longer need to consume uni-directional types. However, the migration isn't complete. We now use RowDocument to store all information instead of Row. We need to reinstate the Row-based approach.
Long-term, the mismatch between converters (Reading Row -> Entity, Writing Entity -> OutboundRow) will be resolved into Entity <-> RowDocument.
Until then, we have to fix this regression. Thanks for letting us know.
We now consider converters for RowDocument. Additionally, we reinstated conversion from R2DBC's Row type into entities as that converter functionality got lost during the converter revision.
Closes#1710
According to the documentation (Overriding Mapping with Explicit Converters) it should be possible to create custom mapper with a Row2Entity converter.
This worked quite well until version 3.2.0. As of this version, all Row ->Entity converters are ignored.
Is this a bug, or intentional, just the documentation not adapted?
The text was updated successfully, but these errors were encountered: