Hey there!
Same issue as discussed here. This problem is based on H2 database compatibility issues. The downside is, the providermanagement module does not use liquibase for database changes, so the solution must be either to find a syntax with compatibility for MYSQL and H2 or to port the module to support liquibase.
However, I created a fixed version for H2 compatibility in my branch
Yes I’ll do that. Any suggestions on the changeset seperation? I’d do one for every create statement, on for the 2 alterations and one for the insert. Also possible would be just one big changeset, because this is our current “state”.
Could you create a ticket + short description?
Here is an example that you could follow: https://github.com/openmrs/openmrs-module-reporting/commit/8387ccb287f4387da553fff0272f0e4d94048fe5
Yes go ahead and create a ticket.