-
Notifications
You must be signed in to change notification settings - Fork 41.1k
Extract database type from JDBC URL and forward to Hibernate #7708
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.
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
Comments
Funny that our documentation states "auto-detected by default". That's quite misleading! |
Hey team, I'm new to the project on github, but have used STS some previously. Would this enhancement be a good place for me to start contributing? Thanks! |
Chris, those issues are typically flagged with |
Previously, property `spring.jpa.database` should be provided. This commit allows to detect the database when `spring.datasource.url` is provided. See spring-projectsgh-7708
Previously, property `spring.jpa.database` should be provided. This commit allows to detect the database when `spring.datasource.url` is provided. See spring-projectsgh-7708
Previously, property `spring.jpa.database` should be provided. This commit allows to detect the database when `spring.datasource.url` is provided. See spring-projectsgh-7708
Previously, property `spring.jpa.database` should be provided. This commit allows to detect the database when `spring.datasource.url` is provided. See spring-projectsgh-7708
Closing in favor of PR #7796 |
Previously, property `spring.jpa.database` should be provided. This commit allows to detect the database when `spring.datasource.url` is provided. Closes gh-7708
* pr/7796: Polish contribution Autodetect spring.jpa.database from spring.datasource.url
It looks like that I have to configure
spring.jpa.database
explicitly when I usespring.datasource.url
. The latter is a common approach when e.g. moving from embedded H2/HSQL to a persistent local one. It would be cool if Boot would derive the value to use for the former based on the JDBC URL configured similar to what it does for the JDBC driver class.The text was updated successfully, but these errors were encountered: