Support using MariaDB JDBC URL to set database name, user and password

[guss77]

Implement feature compatibility with MySQL container requested in issue #949

[kiview]

Hi @guss77, thanks for the PR.
Can you please add the corresponding tests to

testcontainers-java/modules/jdbc-test/src/test/java/org/testcontainers/jdbc/JDBCDriverTest.java

Line 52 in 1d0140a

{"jdbc:tc:mysql:5.5.43://hostname/databasename?useSSL=false", EnumSet.noneOf(Options.class)},

?

[kiview]

Add tests for JDBC driver

[guss77]

Something like this?

[kiview]

Yes, thanks.
Do you know if these check will fail, if you revert the changes you did to MariaDBContainer?

[guss77]

Interestingly enough, without the MariaDbContainer support for user and password, the only test that fails is jdbc:tc:mariadb://hostname/databasename?user=someuser&TC_INITSCRIPT=somepath/init_mariadb.sql on an assert at JDBCDriverTest.java:140 which tests that the "current user" is someuser (hardcoded?).

This actually makes sense to me - this PR is about obeying the configuration from the URL, so without it the container still starts, but uses the "test" username so the only way to check that is to check if the current logged in used matches what we expect from the URL.

The only question is why the other tests with a user in the URL didn't fail, and I think I understand why.

[guss77]

With the last change, all MariaDB tests with a custom user name fail without the PR changes.

[kiview]

Thanks, LGTM to me now.
But for JDBC PRs, it's always good if @rnorth gives it an additional look 🙂

[rnorth]

LGTM, thank you @guss77!