ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Rollback aborts after a deployed schema change I have a changelog where one changeset adds a column with a default value to an existing table, and a later changeset builds on that column. When I run a rollback command targeting the earlier changeset, Liquibase aborts and reports that no rollback was defined for the changeset, leaving the schema untouched. My
We use Ballerina's persist feature to generate type-safe data-access clients and SQL migration scripts from a Ballerina data model, backed by a relational store (PostgreSQL in our case, with MySQL in some environments). Applying model changes forward works well, but the persist tooling does not appear to generate down-migrations or any automated rollback pat
Limits of Vert.x Verticle State Migration During Rollback Goal: Determine whether Vert.x offers a built‑in mechanism to transfer in‑memory verticle state (such as fields, caches, or timers) from a failed version back to a previously known‑good version during a rollback triggered by a health‑check failure. Constraints: Vert.x allows undeploying a verticle and
Goal Deploying a new application version that includes a database schema change requires that the rollback process also revert the migration. PM2’s pm2 deploy command can roll back application code, but it does not touch the database. Constraints and Uncertainty Rollback only reverts the last commit, leaving the database in the new state. A mismatch between
Goal Guarantee that a schema change applied by JHipster can be fully rolled back by Liquibase without manual intervention. Constraints JHipster automatically emits <addColumn> and similar changes but omits <rollback> blocks for operations such as table renames or foreign‑key adjustments. Liquibase requires a valid rollback section to revert a cha
The goal is to allow consumers of a NuGet package to revert to a non‑breaking version after a breaking schema change without having to manually edit version constraints in their project or lock files. NuGet treats each published version as immutable, so rollback depends entirely on the consumer’s version range and any lock‑file constraints. The documented op
Rollback Failure After Database Schema Deployment Azure DevOps Release Pipelines provide a rollback mechanism for database deployment tasks, but this functionality does not guarantee safe restoration of the prior database schema state. When a schema change cannot be automatically reversed, the rollback operation fails with a generic "Rollback failed" error i
ClojureScript applications often persist state via LocalStorage or IndexedDB using native maps or vectors. When a new deployment introduces a schema change to this persisted data and is subsequently rolled back to a previous build, the older code may encounter data structures with unexpected keys or modified nested types. While ClojureScript's dynamic nature
Goal: ensure that a failed Ecto upgrade can be recovered safely when a migration contains irreversible operations such as raw SQL or data transforms. Constraint: the change/0 callback can auto‑reverse only a limited set of commands; any irreversible step raises on rollback, while explicit up/0/down/0 pairs give full control but require more code and duplicat
ballerina
vertx
pm2
jhipster
liquibase
nuget
clojurescript