(feat) Add support for Hikari Datasource #570
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This pull request introduces support for the HikariCP connection pool in the Ebean DAO implementation. The most significant changes are the addition of the HikariCP dependency and logic to handle HikariCP data sources when creating the schema evolution manager configuration.
Dependency management:
externalDependency.hikariCPto thedao-impl/ebean-dao/build.gradledependencies to enable HikariCP support.Schema evolution manager initialization:
EbeanLocalAccess.javato importHikariDataSourcefor type checking and extraction of connection details.createSchemaEvolutionManagermethod inEbeanLocalAccess.javato detect if the Ebean server is using a HikariCP data source and extract the JDBC URL, username, and password accordingly. Falls back to the existing logic if HikariCP is not used.Testing Done
./gradlew build
Checklist