ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #liquibase
When shared dev or staging databases drift, Liquibase changesets can fail with duplicate‑object errors. This post shows how to wrap changesets in preconditions, demonstrates a working example, explains the MARK_RAN trade‑off, and gives practical checks to keep migrations reliable.
Learn how to use Liquibase Contexts to separate environment-specific data from core schema changes, preventing test data from leaking into production databases.
Learn how to add Liquibase preConditions to a changeset to validate table, column, row count, or custom SQL state before applying migrations, with flow control via onFail/onError and verification steps.
Manage database migrations across multiple environments from a single changelog using Liquibase contexts and labels. Learn how to apply changesets conditionally based on environment and feature flags.
Learn how Liquibase contexts let you tag changesets and run only those matching a supplied --contexts argument, with a concrete XML example, verification steps, and common pitfalls.
Schema drift breaks deployments when changelogs assume a single path. Liquibase preconditions check actual database state before running a changeset, letting one changelog adapt across environments—if you choose onFail actions carefully.
A step‑by‑step diagnostic guide for troubleshooting Liquibase validation failures in JHipster‑generated applications, including checks, fixes, and escalation paths.
Learn how to implement a deterministic database migration strategy using Liquibase ChangeSets to eliminate schema drift and ensure deployment stability.
A practical guide to recovering from a failed Liquibase migration by identifying the failed changeset, previewing rollback SQL, applying automatic or manual reversal, and reconciling DATABASECHANGELOG with changelogSync and releaseLocks.
jhipster