runInTransaction

Uses

When you make a database deployment with the update command, Liquibase attempts to create an atomic "transaction block" around each changeset to ensure that it is either fully deployed to the database or not deployed at all. This protects your database from incomplete deployments with unpredictable behavior.

However, your database may not allow certain SQL statements to run in a transaction block, such as CREATE DATABASE in PostgreSQL or ALTER TABLE on an external table in AWS Redshift. If you need to deploy a changeset where this is the case, set runInTransaction to false on that changeset.

Warning: If runInTransaction is set to false and an error occurs part way through running a changeset that contains multiple statements, the Liquibase DATABASECHANGELOG table will be left in an invalid state.

In Liquibase Secure 4.27.0 and later, the CheckRunInTransactionValue policy check is enabled by default so that you can easily confirm whether your changesets have the correct configuration.

Syntax

Note: All changelog attributes use the camelCase format.

Troubleshooting

If you specify a native executor other than JDBC using runWith, you cannot also set runInTransaction to true. If you do, Liquibase throws an UnexpectedLiquibaseException error:

Unexpected error running Liquibase: Migration failed for changeset runwith-tr.sql::1::runSQLTableWithPsql::Liquibase Secure User: Reason: liquibase.exception. DatabaseException: liquibase.exception.LiquibaseException: liquibase.exception. UnexpectedLiquibaseException: psql returned a code of 3