JDBC: Prevent ContainerDatabaseDriver from throwing NPEs when on classpath but not initialized #3976
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.
When
ContainerDatabaseDriver
hasn't been used yet to connect, thedelegate
isnull
. This causes various JDBC metadata methods of the driver to fail with aNullPointerException
. The change prevents this by providing reasonable defaults.As an example, when org.testcontainers:jdbc is on the classpath, but hasn't been used yet, the following produces a
NullPointerException
:The interrogation of the
java.sql.Driver
metadata shouldn't produce a NPE.