You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently using a Mysql driver with no pooling. I was thinking if HikariCP supported access to it through a jdbc url, then in order to integrate HikariCP one would only need to add HikariCP to the classpath and update the jdbc url to a HikariCP jdbc url. Since you don't have many configuration parameters they could all be put on your jdbc url. Then have your users provide the db driver database url as a parameter.
Too crazy? Just close no worries
The text was updated successfully, but these errors were encountered:
That's pretty crazy. 😃 Actually, we're not a fan of URL-based configuration because when the URL starts getting to be 100+ characters because of all the keys and values it gets pretty unmaintainable and prone to errors.
We are currently using a Mysql driver with no pooling. I was thinking if HikariCP supported access to it through a jdbc url, then in order to integrate HikariCP one would only need to add HikariCP to the classpath and update the jdbc url to a HikariCP jdbc url. Since you don't have many configuration parameters they could all be put on your jdbc url. Then have your users provide the db driver database url as a parameter.
Too crazy? Just close no worries
The text was updated successfully, but these errors were encountered: