The modifyChangeSets Change Type lets you include SQL scripts in your Liquibase changelog while using an application's native executor—like PSQL, SQL Plus, or SQLCMD—instead of the JDBC default— to deploy raw SQL scripts with a native executor. This removes the burden of converting raw SQL scripts into formatted SQL changelogs. You can use it to specify an overarching executor for all files in your project.


If you have many changesets that need to be run with a native executor, and you organize your changelogs in a "root" and "nested" format using the include and includeAll tags, you can use the runWith attribute (PSQL, SQLPlus, or SQLCMD) to specify an executor that applies to every changeset in every file wrapped in the modifyChangeSets tag. Since your nested changelogs inherit the executor specified in modifyChangeSets, you don't have to specify it on each individual changeset you include.

Note: include and includeAll changetypes are available only in structured changelogs (XML, YAML, JSON). This is an existing limitation not introduced by modifyChangeSets.

If you want to make an exception for a particular changeset you're including, you can specify the default Liquibase JDBC executor for that changeset. All other changesets still run with the executor inherited from modifyChangeSets.

You can still include additional files in your root changelog outside of the modifyChangeSets tag. These files run with the Liquibase JDBC executor.



Attribute Value Notes
runWith jdbc Default value if none specified. See Class JdbcExecutor.
psql Executor for PostgreSQL. See Use PSQL and runWith on PostgreSQL.
sqlplus Executor for Oracle. See Use SQL Plus and runWith on Oracle and Use SQL Plus and Oracle Proxy User.
sqlcmd Executor for MSSQL Server. See Use SQLCMD and runWith on MSSQL Server.
<custom> Custom executor. See Additional "runWith" Options.

Related links