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
The docs state that R2dbcConverter is recommended to do most of the work.
R2dbcConverter however must be obtained via ReactiveDataAccessStrategy.
This is fine, but should be documented, as I did expect R2dbcConverter to be readily available as a Bean when being so heavily advertised.
The text was updated successfully, but these errors were encountered:
ReactiveDataAccessStrategy originates from having DatabaseClient using a pluggable data access strategy. Now that DatabaseClient went into Spring Framework and we have a proper R2dbcEntityTemplate, we no longer need ReactiveDataAccessStrategy and can move its parts into R2dbcConverter. A good first step would be exposing getConverter() on R2dbcEntityOperations to align with the other Spring Data modules.
ReactiveDataAccessStrategy is now deprecated in favor of using StatementMapper, UpdateMapper, and R2dbcConverter directly. The access strategy interface was introduced to allow pluggable access strategies in DatabaseClient. With moving DatabaseClient into Spring Framework, this approach is no longer required.
mp911de
changed the title
Document that R2dbcConverter must be obtained through ReactiveDataAccessStrategy
Register R2dbcConverter bean and deprecate ReactiveDataAccessStrategy
Sep 8, 2020
I repurposed this ticket to align our converter infrastructure with the other Spring Data modules. R2dbcConverter is now registered as bean and ReactiveDataAccessStrategy is deprecated.
The docs state that R2dbcConverter is recommended to do most of the work.
R2dbcConverter however must be obtained via ReactiveDataAccessStrategy.
This is fine, but should be documented, as I did expect R2dbcConverter to be readily available as a Bean when being so heavily advertised.
The text was updated successfully, but these errors were encountered: