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
RelationalMappingContext should maintain mapping metadata for user-types that have custom converters registered and are considered simple types by the SimpleTypeHolder.
Coming from R2DBC, one might want to register a custom converter for read/write customization but still want to use @Table annotations or NamingStrategy in the context.
Right now, we do not create a PersistentEntity hence metadata cannot be used.
We should also consider that Dialect may also contribute simple types so we should not register mapping metadata for these types
Mark Paluch opened DATAJDBC-375 and commented
RelationalMappingContext
should maintain mapping metadata for user-types that have custom converters registered and are considered simple types by theSimpleTypeHolder
.Coming from R2DBC, one might want to register a custom converter for read/write customization but still want to use
@Table
annotations orNamingStrategy
in the context.Right now, we do not create a
PersistentEntity
hence metadata cannot be used.We should also consider that
Dialect
may also contribute simple types so we should not register mapping metadata for these typesNo further details from DATAJDBC-375
The text was updated successfully, but these errors were encountered: