When we generate the SQL statements for a changeset, the updates/Inserts to the DATABASECHANGELOG table also are created. This is good, but in case the SQL statement fails, still the change log statement is executed leaving the database in a inconsistent state even from a Liquibase perspective. Can these SQL generated also include transaction statements to avoid this?
-
Learn
-
Resources
-
Free Tools
OSS Risk Scanner Database DevOps Risk AssessmentCheat Sheets
Snowflake + Liquibase Databricks + Liquibase -
eBooks
6 Liquibase Community Risks & How to Avoid Guide: SOC 2 Compliance at the Database Layer Guide: Quantify the Value of Liquibase Secure -
Comparison Guides
Liquibase vs. Flyway Liquibase vs. Bytebase Liquibase Community vs Liquibase Secure
-
- Quickstart
- Get Started
- Documentation
- University
-
Resources
- Connect
- Contribute
- Join
- Blog