ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal: Assess whether Ecto can guarantee that a migration’s down function restores the database to its pre‑migration state after a schema change Ecto runs each migration inside a single transaction, but the generated down callback does not automatically undo data modifications that occur before the schema alteration. Certain schema operations—such as changing
When a deployment on DisCloud fails, the platform’s web‑based log viewer aggregates the agent’s output, showing status messages, timestamps, and a truncated snippet of the last executed command. The UI offers a Rollback button that attempts to revert the site to the previous successful deployment, but the logs do not clearly indicate whether the rollback suc
I'm planning a schema migration on SQL Server (Enterprise Edition, recent version) that alters a large, heavily queried table. Two documented approaches are on the table: an online index rebuild with ONLINE = ON , which permits concurrent DML, or an offline change wrapped in BEGIN TRANSACTION so the DDL can roll back if anything fails mid-deployment. The ten
Problem The goal is to determine whether tRPC can safely roll back or tolerate a breaking schema change without causing client‑side validation failures. Currently, when a procedure’s Zod schema is altered—for example, by changing an optional field to required—the server validates incoming requests against the new schema and throws a ZodValidationError if the
When executing pulumi upgrade , the CLI downloads and installs provider plugins into the local .pulumi/cache directory. If the process aborts mid-download or a plugin fails to initialize, the stack may remain in a failed state while the new plugin files persist in the cache. The current recovery workflow requires manual intervention: uninstalling the failed
After an ALTER TABLE ... CHANGE, ADD, or DROP COLUMN, the Hive metastore immediately records the new column definitions while the underlying data files remain unchanged, creating a schema‑metadata mismatch. The objective is to provide a safe rollback that restores both metadata and data to a consistent state without manual re‑creation of the table or re‑load
Goal After a plugin that adds custom types via createSchemaCustomization is removed, a developer wishes to roll back the GraphQL schema to its prior state using Gatsby’s schema‑snapshot feature. Uncertainty The Gatsby documentation states that a snapshot captures the schema after all plugins run, but it does not specify whether a restore also re‑installs the
Goal Determine whether Okta's automatic rollback restores custom SAML attribute statements and third-party integration configurations when a major version upgrade fails within the two-hour window. Constraints and uncertainty Okta documents that in-place upgrades create a pre-upgrade backup and support rollback within two hours. However, the documentation not
Goal We want to ensure that a rollback routine executed via Aff.bracket or Aff.try runs even if the Aff is cancelled before completion, such as during a schema migration that aborts due to a conflict. Current Observation When an Aff is cancelled using Async.cancelUnless , the release action supplied to bracket may not execute, leaving the database in an inco
ecto
microsoftsqlserver
pulumi
hadoop
gatsby
graphql
okta