Hey, after 2 years, H2 released a new version: 2.0.202, which has some incompatibles.
Should Exposed support both versions, or only the latest one? Often, H2 db's are used for testing, so supporting latest version only would be possible. The maintainer of H2 also support the latest version only and won't backport any fixes.
Currently, I tried to adopt the versions changes in Exposed and I have some problems with the MySQL mode, because it is very buggy from H2 and fixes are only available in latest H2 version.
12/08/2021, 1:23 PM
Probably a good idea to have a separate maven repo for h2 version 2...
Just upgrading the current module might break things and not everybody is interested in upgrading (especially when using h2 for test code that works...)?
12/08/2021, 1:26 PM
Current implementation uses a new dialect, like mysql5 and mysql8.
The H2 driver used in exposed-tests are never shared with exposed-core, like every driver else. So it won't ("shouldn't") break consumers code