-
Notifications
You must be signed in to change notification settings - Fork 35
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
Play way is not correct #3
Comments
Hmmm, it may the documentation that should be more accurate. I eventually found the required settings in HikariCPConfig I cannot switch to Hikari proeprty file as, as I am using some features of TypesafeConfig in my db url. |
Yes, the docs are wrong. I will probably close this issue after #4, since I will need to remap BoneCP properties to HikariCP avoiding deprecated properties. |
By the way, about this:
Could you please elaborate about which features are you using that prevents you to use a properties file? Is this change enough to enables you to migrate to a properties file? |
I do something like this, the mysql.url-params are the culprit here:
|
Hum, that is already supported in the current release (1.2.0), you can both reference another property (using Here is what is supported by commons configuration, which is used to read the hikaricp.properties file: |
Anyway, I will leave this issue open because we need to correct the docs. |
Ah yes, my example was not precise enough. I have mysql.url-params defined in application.conf (Typesafe Config), and are referencing it in all the other config files - but commons configuration will not read references from the "parent" configuration. I am trying to achieve that I only have to specify these parameters once, at reference it from all other mysql configurations. |
Support for embedded Typesafe Config would be great. Then something like this:
What do you think? |
Sounds good. Maybe we could ditch the translation of bonecp->hikaricp in favor of this option. Also, since Typesafe Config supports environment variables, we could use it instead of commons configuration. |
Master branch already has dropped the translation from bonecp to hikaricp. |
In HikariCPConfig the maxPoolSize is incorrect. Should it not be the following in line 82:
The same goes for the minPoolSize in line 88.
The text was updated successfully, but these errors were encountered: