ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
An architecture note on Liquibase changeset checksums: what the hash covers, the trust boundary it enforces, safe override patterns, and when to redesign around it.
A step‑by‑step diagnostic guide for Liquibase checksum validation failures, covering MD5 vs SHA‑256 mismatches, encoding drift, manual DB edits, version upgrades, and duplicate changesets, with ordered checks, targeted fixes, and escalation thresholds.
Administrators need to verify that restored data matches the source archive by applying checksum validation, but the current Automated backup restoration validation feature only offers a global on/off switch that is undocumented in the management console and unavailable per backup set. In releases before 2.4 the feature omits checksum validation entirely, wh
Diagnose why Liquibase blocks an update after an already-deployed changeset is edited, and decide whether to clear the affected checksum, review and approve the change, or disable checksum validation. Liquibase stores a checksum for each executed changeset in DATABASECHANGELOG and runs validation by default before update and related commands. Editing an exec
sema