In production I’m using Oracle and all my changelogs have been written with Oracle in mind.
In my development environment I’m trying to generate the changelogs on an H2 instance in Oracle compatibility mode.
My problem is that Liquibase is validating against H2, not Oracle.
Is there a way of forcing Liquibase to validate against Oracle even though the url looks like an H2 one?
My biggest headaches are regarding sequences and dropNotNullConstraint.
Liquibase version: 2.0.5
conneciton url: jdbc:h2:tcp://localhost:9092/test;MODE=Oracle;AUTO_SERVER=TRUE;DB_CLOSE_DELAY=-1
any help would be greatly appreciated