ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #liquibase
Goal Determine how to roll back a database that has experienced a partial changeSet failure while preserving data integrity. Constraints Liquibase records a changeSet in DATABASECHANGELOG only after a successful run; a failed changeSet is omitted. Rollback relies on timestamps; if a changeSet failed mid‑execution, its timestamp is missing, making the target
Testing Migrations Without Exposing Production Credentials The goal is to validate Liquibase changesets in a sandbox while avoiding any use of live production credentials. Liquibase 4.25 introduces the rollbackSQL command, which outputs the exact SQL needed to revert a changeset. By pointing Liquibase at an in‑memory H2 database or a Docker‑based MySQL 8.0 i
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
The goal is to clarify how Liquibase sequences custom changes—particularly Java code changesets and SQL changesets—when a rollback is interrupted before completion, and whether the thrown MigrationFailedException indicates which changeset was partially rolled back. Because the framework does not explicitly document the ordering rule for mixed change types, t
Goal Determine whether a restored database backup can be considered in sync with the Liquibase changelog without generating false pending changesets due to backup‑time context or label settings. Constraints include the possibility that the backup was taken while a specific context or label was active, which may cause Liquibase’s validation and drift‑detectio
Goal: configure Liquibase so that a transient failure of a changeSet does not lead to duplicate inserts or updates when the changelog is rerun. Constraints: the solution must work with the existing lockWaitTimeout and retryCount mechanisms, must not rely on manual intervention, and must consider whether the changeSet is idempotent or not. Using preConditions
Problem During a new deployment of a JHipster‑generated Spring Boot application, the application aborts during startup, immediately after the Liquibase migration step. The log shows either a ValidationFailedException mentioning a changeset id and author, or a LockException indicating the change‑log lock cannot be acquired. Goal Identify the root cause of the
Liquibase marks a changeset FAILED when any statement inside it errors, then re-executes the entire changeset on the next run. This guarantees retry safety only when each changeset contains a single logical change, because the DATABASECHANGELOG record prevents re-running an EXECUTED changeset. Teams that prefer fewer, coarser changesets must instead make eve
In multi‑file Liquibase projects the same id and author can appear in several changelog files. The databasechangelog table records each execution, but the uniqueness rule that triggers duplicate warnings is not clearly documented. Historically, some releases logged a warning when the same id and author were found in more than one file, yet the later instance
jhipster