It's not necessary to overwrite getConnectionSchemaName() if supportsSchemas returns true? Nice to know and that part seems to work now. I've just fetched the latest change from github.
Using that latest version I now get
- Caused by: liquibase.exception.LockException: liquibase.exception.UnexpectedLiquibaseException: Don't know how to query for sequences on MYSCHEMA @ jdbc:sapdb://maxdb001:7210/MAX
- at liquibase.lockservice.StandardLockService.acquireLock(StandardLockService.java:209)
- at liquibase.lockservice.StandardLockService.waitForLock(StandardLockService.java:148)
- at liquibase.Liquibase.update(Liquibase.java:189)
- at liquibase.Liquibase.update(Liquibase.java:181)
- at org.nowhere.test.DBServlet.applyTemplate(DBServlet.java:177)
- ... 50 more
- Caused by: liquibase.exception.UnexpectedLiquibaseException: Don't know how to query for sequences on MYSCHEMA @ jdbc:sapdb://maxdb001:7210/MAX
- at liquibase.snapshot.jvm.SequenceSnapshotGenerator.getSelectSequenceSql(SequenceSnapshotGenerator.java:106)
- at liquibase.snapshot.jvm.ext.SequenceSnapshotGeneratorHana.getSelectSequenceSql(SequenceSnapshotGeneratorHana.java:22)
- at liquibase.snapshot.jvm.SequenceSnapshotGenerator.snapshotObject(SequenceSnapshotGenerator.java:55)
- at liquibase.snapshot.jvm.ext.SequenceSnapshotGeneratorHana.snapshot(SequenceSnapshotGeneratorHana.java:35)
- at liquibase.snapshot.SnapshotGeneratorChain.snapshot(SnapshotGeneratorChain.java:47)
- at liquibase.snapshot.jvm.JdbcSnapshotGenerator.snapshot(JdbcSnapshotGenerator.java:62)
- at liquibase.snapshot.SnapshotGeneratorChain.snapshot(SnapshotGeneratorChain.java:47)
- at liquibase.snapshot.jvm.JdbcSnapshotGenerator.snapshot(JdbcSnapshotGenerator.java:62)
- at liquibase.snapshot.SnapshotGeneratorChain.snapshot(SnapshotGeneratorChain.java:47)
- at liquibase.snapshot.jvm.JdbcSnapshotGenerator.snapshot(JdbcSnapshotGenerator.java:62)
- at liquibase.snapshot.SnapshotGeneratorChain.snapshot(SnapshotGeneratorChain.java:47)
- at liquibase.snapshot.DatabaseSnapshot.include(DatabaseSnapshot.java:131)
- at liquibase.snapshot.DatabaseSnapshot.<init>(DatabaseSnapshot.java:36)
- at liquibase.snapshot.JdbcDatabaseSnapshot.<init>(JdbcDatabaseSnapshot.java:24)
- at liquibase.snapshot.SnapshotGeneratorFactory.createSnapshot(SnapshotGeneratorFactory.java:129)
- at liquibase.snapshot.SnapshotGeneratorFactory.createSnapshot(SnapshotGeneratorFactory.java:122)
- at liquibase.snapshot.SnapshotGeneratorFactory.createSnapshot(SnapshotGeneratorFactory.java:110)
- at liquibase.snapshot.SnapshotGeneratorFactory.has(SnapshotGeneratorFactory.java:100)
- at liquibase.snapshot.SnapshotGeneratorFactory.hasDatabaseChangeLogLockTable(SnapshotGeneratorFactory.java:169)
- at liquibase.lockservice.StandardLockService.hasDatabaseChangeLogLockTable(StandardLockService.java:134)
- at liquibase.lockservice.StandardLockService.init(StandardLockService.java:80)
- at liquibase.lockservice.StandardLockService.acquireLock(StandardLockService.java:182)
- ... 54 more|
BTW: What I'm testing here: We have ~40 change sets that we used with liquibase 2.0.5. We're trying to upgrade to liquibase 3.x as we need to support HANA as alternative DB. I'm simply trying to run our existing change set to a MaxDB (version 7.8.2.34) with the new liquibase version.
I've tried changing supportSequence() to return false in MaxDBDatabase, and that seems to work, but now I'm running into a strange error where a second instance of the web application tries to recreate the DATABASECHANGELOGLOCK table from StandardLockService.acquireLock and fails with a "Duplicate table name:DATABASECHANGELOGLOCK" error... I'm checking what goes wrong there.