Resolve excessive JDBC container creation when using pools and driverClassName #195
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rnorth
force-pushed
the
fix-jdbc-driver-initialization
branch
2 times, most recently
from
3f3ed49
to
c5a24cd
Compare
rnorth
changed the title
rnorth
force-pushed
the
fix-jdbc-driver-initialization
branch
from
c5a24cd
to
5ed5325
Compare
Extend test suite to include more rigorous testing of connection pools with containers
rnorth
force-pushed
the
fix-jdbc-driver-initialization
branch
from
4de4422
to
f1bc5c6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Extend test suite to include more rigorous testing of connection pools with containers