Skip to content

Upgrade client support to R2DBC 1.0 #28787

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.

Sign up for GitHub

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

Jump to bottom
Closed
sbrannen opened this issue Jul 11, 2022 · 0 comments
Closed

Upgrade client support to R2DBC 1.0 #28787

sbrannen opened this issue Jul 11, 2022 · 0 comments
Assignees
@jhoeller
Labels
in: data Issues in data modules (jdbc, orm, oxm, tx) type: dependency-upgrade A dependency upgrade
Milestone
6.0.0-M5

Comments

@sbrannen
Copy link
Member

This is a follow up to #28059.

Since R2DBC 1.0 has been released, we should upgrade and ensure compatibility with 1.0 for Spring Framework 6.0.

For example, io.r2dbc.spi.Result.getRowsUpdated() returned Publisher<Integer> in 0.9 and apparently returns Publisher<Long> in 1.0.
@sbrannen sbrannen added in: data Issues in data modules (jdbc, orm, oxm, tx) type: enhancement A general enhancement type: dependency-upgrade A dependency upgrade labels Jul 11, 2022
@sbrannen sbrannen added this to the 6.0.0-M6 milestone Jul 11, 2022
@jhoeller jhoeller self-assigned this Jul 11, 2022
@jhoeller jhoeller removed the type: enhancement A general enhancement label Jul 11, 2022
@jhoeller jhoeller modified the milestones: 6.0.0-M6, 6.0.0-M5 Jul 11, 2022
@sjohnr sjohnr mentioned this issue Jul 11, 2022
Closed
@linghengqian linghengqian mentioned this issue Sep 22, 2022
Closed
jhoeller added a commit that referenced this issue Nov 11, 2022
@jhoeller
Upgrade to R2DBC H2 1.0.0
9d1dfc7 
See gh-28787
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jhoeller jhoeller

Labels
in: data Issues in data modules (jdbc, orm, oxm, tx) type: dependency-upgrade A dependency upgrade
Projects
None yet
Milestone
6.0.0-M5
Development

No branches or pull requests
2 participants
@sbrannen @jhoeller