ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
A repository that tracks schema migrations needs a defined rollback safety net: if a migration commit has to be undone weeks after it landed, the pre-change state should still be recoverable. The mechanism under consideration is Git's reflog, which records HEAD movements for a configurable retention period, 90 days by default, adjustable through gc.reflogExp
I'm writing a script for PostgreSQL and since I want it to be executed atomically, I'm wrapping it inside a transaction. I expected the script to look something like this: BEGIN -- 1) Execute some valid actions; -- 2) Execute some action that causes an error. EXCEPTION WHEN OTHERS THEN ROLLBACK; END; -- A.k.a. COMMIT; However, in this case pgAdmin warns me a
RocksDB performs format upgrades lazily on open when a newer library version implies a newer on-disk layout. The upgrade rewrites MANIFEST and SST metadata rather than requiring an explicit upgrade command, and the change is effectively one-way. Once the MANIFEST is rewritten for a newer format, older RocksDB binaries typically cannot open the database, so d
Goal Make changes to bower.json by bower install --save atomic so that a partial write caused by an interruption is automatically reverted, keeping the manifest either fully updated or unchanged. Constraints and uncertainty The current implementation updates bower.json in place without a backup or transaction log, as documented. If the process is killed or f
Recovery Goal To revert a production org to its pre‑upgrade state after a failed Salesforce major release while preserving custom metadata, integrations, and data integrity. Current Constraints The Upgrade Readiness Check identifies impacted components, but once the org has been upgraded, documentation provides no automated rollback path. The only documented
NixOS creates a separate GRUB entry for each system generation, allowing a manual rollback to a known‑good state after a failed upgrade. However, the project has not defined a default policy for automatically booting the previous generation when the system fails to start. The decision must balance safety against the risk of repeatedly booting a broken genera
Goal Recover the node to a stable state after a :release_handler upgrade fails. Constraints OTP’s release handler does not provide an automatic rollback. A failed callback leaves the node with a mixture of old and new modules. The decision to purge or keep partially loaded code is unclear, and the semantics of :code.purge vs :code.load_file differ across OTP
Our Grails application uses the database-migration plugin (Liquibase-based) with changelogs under grails-app/migrations, and we are standardizing how schema changes ship to production. The goal is a rollback story that actually works when a release must be reverted, not just one that exists on paper. The uncertainty is around destructive changeSets. Liquibas
When a dataset owner modifies a schema and creates a new version, Kaggle lets them later set an earlier version as the active one for new notebooks. Existing notebooks continue to reference the version they were originally tied to, but any notebook that relies on the active version may suddenly encounter missing columns or altered types after a rollback. Bec
Asked · 20 Jan 2023, 19:44 UTC
answered · 23 Jan 2023, 19:44 UTC
git
postgresql
json
salesforce
nixos
liquibase
kaggle