Support H2 2.0
See original GitHub issueAfter 2 years, H2 released a new version: 2.0.202
, which has some incompatibles.
Should Exposed support both versions, or only the latest one only? Often, H2 db’s are only used for testing, so supporting latest only would be possible. The maintainers of H2 also only support the latest version and won’t backport any fixes.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:5
- Comments:10 (3 by maintainers)
Top Results From Across the Web
Migration to 2.0 - H2 Database Engine
Migrating an old database to the new version works most of the times. However, there are a couple of important changes in the...
Read more >H2 version change issue from 1.4.200 to 2.0.202?
I upgraded my springboot H2 dependency from 1.4.200 to 2.0.202 , but getting the below exception . Could you please help.
Read more >H2 usage in test scope: v2.0.x not compatible to JPA ...
In my project junit tests manages their own test data and I let the databasemodell be generated by JPA in test scope, so...
Read more >Camunda not compatible with h2 2.0.202+
Updating h2 to 2.0.202+ leads to: org.camunda.bpm.engine.context - ENGINE-16004 ... There is work in progress to support h2 2.0.x database.
Read more >H2 - Flyway by Redgate • Database Migrations Made Easy.
URL format, jdbc:h2:file. Ships with Flyway Command-line, Yes. Maven Central coordinates, com.h2database:h2:2.0.206. Supported versions, 1.2.137 and later.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Is this issue got fixed?
I’m also facing the same issue
db.core.internal.exception.FlywaySqlException: Unable to determine H2 compatibility mode
SQL State : 42001 Error Code : 42001 Message : Syntax error in SQL statement “SELECT VALUE[*] FROM INFORMATION_SCHEMA.SETTINGS WHERE NAME = ‘MODE’”; expected “TOP, DISTINCT, ALL, , NOT, EXISTS, INTERSECTS, UNIQUE”; SQL statement: SELECT VALUE FROM INFORMATION_SCHEMA.SETTINGS WHERE NAME = ‘MODE’ [42001-202]
https://github.com/JetBrains/Exposed/wiki/Getting-Started#maven