As Steve says, this is something we need to do in a very careful way. It’s true that currently we’re much too fussy and reject type conversions that are completely safe.

But we can’t solve this issue by just arbitrarily disabling checks in an undisciplined way.

Instead we need to write down and properly document which implicit type conversions are allowed by design and ensure that they work portably across databases. That is we need a spec and tests.

I see that there is at least one pull request currently opened. I think we should not integrate any such PRs until we have a proper spec.

Also we need to pay careful attention to what happens when you changed preferred JDBC type code mappings.

Personally I think we would be better up opening a Discussion about this.