Open sirius322 opened 10 months ago
At the time I last updated the plugin, Liquibase 4.16.1 was current, and the default-schema-name
was not part of that release from what I can tell. It isn't in the source code for Liquibase (hence my comment in the plugin), and it doesn't come back when I do liquibase generate-changelog --help
.
The solution is to update the plugn again to sync it up with the latest CLI. If I'm lucky, they only added options and didn't remove any...
I have updated Liquibase from 4.17.0 to 4.23.1 and the plugin from 2.0.4 to 2.2.0.
Now I have trouble migrating my activity for generating a changelog from an existing schema. Before the update I used the
defaultSchemaName
argument. With the new version a changelog with a dummy changeset is being generated. The current source code states that the liquibase command doesn't take thedefault-schema-name
argument.However, when used directly
liquibase generate-changelog --help
still lists the argument and works as expected when applied directly.defaultSchemaName
is not supported by the Gradle plugin?Two things that I have tried so far :
-PliquibaseExtraArguments="default-schema-name=SCHEMANAME"
had no effectdefaultSchemaName
withschemas
produces a changelog but adds the source schema as areferencedTableCatalogName
to theaddForeignKeyConstraint
(<addForeignKeyConstraint ... referencedTableCatalogName="SCHEMANAME"/>
). This causes an error when Liquibase Update is run with a different schema/database.