ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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.
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.
Step‑by‑step guide to generate a Liquibase changelog from an existing database using the diffChangeLog command, including prerequisites, execution, verification, and recovery.
Configure Liquibase changeLogFile with classpath-relative paths to ensure migrations work across environments. Learn the changelog structure, tracking mechanism, and common pitfalls to avoid.
Formatted SQL keeps migrations in plain SQL while Liquibase handles tracking, preconditions and rollback — provided you declare rollback and keep applied changesets immutable.
Learn how Liquibase’s automatic rollback works, what trust boundaries it enforces, and how to verify safe rollbacks in practice.
A decision guide for picking Liquibase changelog formats: structured (YAML/XML/JSON) vs. formatted SQL. Covers portability, rollback, reverse engineering, team skills, and a concrete validation workflow with commands you can run today.
maven