Skip to content
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

feat: A better way of discovering the infrastructure beans #176

Closed
mipo256 opened this issue Feb 17, 2025 · 0 comments
Closed

feat: A better way of discovering the infrastructure beans #176

mipo256 opened this issue Feb 17, 2025 · 0 comments

Comments

@mipo256
Copy link
Contributor

mipo256 commented Feb 17, 2025

Currently, we register the YdbDialectProvider via spring.factories. This approach is kind of wacky since it only works when the user is actually using the Spring Boot.

Maybe, because of YdbMappingJdbcConverter should be applied every time to consider @YdbType, we can rely on the fact that user will always have to extend the AbstractYdbJdbcConfiguration.

Related: #173 #174 #175

CC: @KirillKurdyukov
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Moved dialect resolution logic into JdbcConfiguration mipo256/ydb-java-dialects
2 participants
@KirillKurdyukov @mipo256