There are likely two issues:
in test, CONVERT_TO_NULL is added only for MySQL8Dialect +, older dialects uses convertToNull
NPE in org.hibernate.engine.jdbc.connections.internal.BasicConnectionCreator
real error is
MySQL 5.5 - org.hibernate.dialect.MySQL5InnoDBDialect (I know I should have used MySQL55Dialect)
MySQL 5.7 - org.hibernate.dialect.MySQL57Dialect
I'm wondering if the issue is not that you use a very recent driver.
I wouldn't expect these old dialects to be compatible with this version of the driver. And I'm not sure we can be compatible with both versions of the driver (people using MySQL 5.7 probably also use an old driver).
yeah, that would be the case, it passes with mysql-connector-java-5.1.42-bin.jar
could you simply try to remove the zeroDateTimeBehavior option altogether?
I don't think it's useful at all in this test case, considering we don't set zero dates. The purpose of this test is to test custom time zone configuration and we don't need that option to do that.
> but I see it was added in 5cfb0a508cf7 as part of support of some MySQL 8 feature
Not really, it was just adapted to also make it work with MySQL 8. The zeroDateTimeBehavior=convertToNull was present before.
The option was present in the original JDBC URL of the person complaining in https://hibernate.atlassian.net/browse/HHH-11396 but it has no value for this test.
I'm going to remove it.