I'd like to use offline mode to supply my customers with an initial SQL script to set up a database. They use this script to quickly "drop everything" and recreate the test environment.
Every release we do contains incremental SQL scripts, created with updateSQL against a database created with Liquibase up to the point of the previous release.
The problem is that updateSQL in offline mode does not create the DATABASECHANGELOCKLOCK table. But the incremental SQL scripts assume it does exist.
The fix would be to create DATABASECHANGELOGLOCK in offline mode also. (Or make it configurable, like the 'outputLiquibaseSql' parameter.)
Liquibase 3.6.3, Oracle or PostgreSQL