Skip to content

AbstractR2dbcConfiguration should use R2dbcMappingContext instead of RelationalMappingContext #311

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
mp911de opened this issue Feb 20, 2020 · 0 comments
Closed

AbstractR2dbcConfiguration should use R2dbcMappingContext instead of RelationalMappingContext #311

mp911de opened this issue Feb 20, 2020 · 0 comments
Labels
type: bug A general bug
Milestone
1.1 M4 (Neumann)

Comments

@mp911de
Copy link
Member

mp911de commented Feb 20, 2020

To avoid non-unique bean lookup failures, we should require R2dbcMappingContext instead of RelationalMappingContext in AbstractR2dbcConfiguration.
@mp911de mp911de added the type: bug A general bug label Feb 20, 2020
@mp911de mp911de added this to the 1.1 M4 (Neumann) milestone Feb 20, 2020
mp911de added a commit that referenced this issue Feb 20, 2020
@mp911de
#311 - Use R2dbcMappingContext in AbstractR2dbcConfiguration instead …
7ed68ee 
…of RelationalMappingContext.

We use now a more concrete type in the configuration to avoid clashes when Spring Data JDBC is on the class path.
@mp911de mp911de closed this as completed Feb 20, 2020
@mp911de mp911de mentioned this issue Feb 20, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: bug A general bug
Projects
None yet
Milestone
1.1 M4 (Neumann)
Development

No branches or pull requests
1 participant
@mp911de