-
Notifications
You must be signed in to change notification settings - Fork 682
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
Use HikariCP instead of c3p0 connection pool #994
Comments
asolntsev
added a commit
to codeborne/play
that referenced
this issue
Jun 2, 2017
… DBBrowserPlugin * it has a totally different responsibility, and * it could disable itself in prod mode
asolntsev
added a commit
to codeborne/play
that referenced
this issue
Jun 2, 2017
…e class C3P0Plugin * it will allow user to use other implementations instead of c3p0 (for example, HikariCP)
asolntsev
added a commit
to codeborne/play
that referenced
this issue
Jul 16, 2017
… DBBrowserPlugin * it has a totally different responsibility, and * it could disable itself in prod mode
asolntsev
added a commit
to codeborne/play
that referenced
this issue
Jul 16, 2017
…e class C3P0Plugin * it will allow user to use other implementations instead of c3p0 (for example, HikariCP)
asolntsev
added a commit
to codeborne/play
that referenced
this issue
Jul 21, 2017
… DBBrowserPlugin * it has a totally different responsibility, and * it could disable itself in prod mode
Merged |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
HikariCP is fresh and fast, while c3p0 is old and unsupported.
https://brettwooldridge.github.io/HikariCP/
To keep compatibility, we Play 1.4.x could support both c3p0 and HikariCP, so that users can configure which one they want to use. c3p0 could be the default option for the compatibility.
The text was updated successfully, but these errors were encountered: