CODEWITHSUNDEEP
liquibase
kothvandir
kothvandir

Reputation: 2161

updateSQL command precedes databasechangelog table with current schema name

When I execute the sqloutput command, liquibase 3.2.2 precedes each insert on databasechangelog table with current schema name.

INSERT INTO <MY_TEST_SCHEMA>.DATABASECHANGELOG (ID, AUTHOR, FILENAME, DATEEXECUTED, ORDEREXECUTED, MD5SUM, DESCRIPTION, COMMENTS, EXECTYPE, LIQUIBASE) VALUES (...);

This forces me to process the outcome files to remove the "MY_TEST_SCHEMA." string, because we execute liquibase against a test schema before we launch the resulting files to production.

I've been using liquibase 2.0.3 for quite long and this behaviour is new in liquibase 3.0.0.

Is there any way to prevent liquibase from adding the schema name? I've already tried to use the defaultSchemaName parameter but it didn't work.

Upvotes: 0

Views: 527

Answers (1)

Nathan Voxland
Nathan Voxland

Reputation: 15763

You should be able to use the --outputDefaultSchema=false and --outputDefaultCatalog=false flags to suppress them being included.

It looks like the flag is not followed, at least from the command line in 3.2.2. I created https://liquibase.jira.com/browse/CORE-2088 and added a fix for 3.3.0 which should be out in the next week or so.

Upvotes: 1

Related Questions