ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #liquibase
Use Liquibase preconditions to check database state before applying migrations. Learn how to embed them, test with --dryRun, and avoid common pitfalls in this concise guide.
SQLcl replaces SQL*Plus with JavaScript/TypeScript scripting, embedded Liquibase, and JSON output — making Oracle automation work in modern CI/CD pipelines. Includes a worked example and the trade-offs you'll hit.
Learn how Liquibase preconditions guard migrations against duplicate changes, with a real example, trade‑offs, and best practices to keep your database in the expected state.
Configure Liquibase changeLogFile with classpath-relative paths to ensure migrations work across environments. Learn the changelog structure, tracking mechanism, and common pitfalls to avoid.
Use one master changelog with contexts for environment gating and preconditions for state assumptions. Keep DATABASECHANGELOG as the source of truth and plan for locks, partial DDL, and precondition masking.
A step‑by‑step diagnostic guide to identify why Liquibase reports a successful update but the database schema remains unchanged or fails to roll back.
Learn how Liquibase contexts let you maintain a single changelog while applying environment‑specific changesets safely, with a concrete example, verification steps, and trade‑offs.
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.
sqldeveloper
maven
java