ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
We are planning a schema migration for a small MySQL 8.0 application and want to avoid visible downtime. The plan uses ALTER TABLE with ALGORITHM=INPLACE and LOCK=NONE , documented to permit concurrent DML for most of the operation. However, MySQL still requires a brief exclusive metadata lock at the start and end of the DDL to install the new table definiti
SourceEngine Schema Evolution The versioned schema management system tracks applied schema revisions for controlled evolution. The uncertainty lies in the atomicity guarantee when a schema change is followed by a rollback. What is the documented behavior for transactional boundaries during schema rollback? Does the system ensure data integrity across schema
NetBox’s backup and restore management commands produce and consume JSON exports that track all objects, but the JSON schema differs significantly between NetBox 3.x and 4.x. When restoring a 3.x export into a 4.x instance, the restore process may encounter validation failures if the target version lacks fields present in the backup, or if schema migration s
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
Evaluate rollback safety after a schema-changing upgrade in pfSense 2.7.x and later, where the configuration database schema version is tracked in /conf/version.xml and upgrades trigger migration scripts that rewrite tables. The documented restore path only replaces config.xml. It does not revert the underlying schema changes, so the database can remain in a
Problem Statement When migrating a small Oracle application, the goal is to apply schema changes without taking the application offline. Oracle SQL Developer’s Database Diff tool can compare two schemas and produce DDL scripts, but it currently lacks an incremental diff mode that would identify only new or modified objects since the last sync. Because the ge
Deploying a schema change that includes irreversible data migrations forces a choice between two Dynatrace remediation paths: allowing Release Guardian to trigger an automatic rollback when service-level objectives are breached, or inserting a manual approval task in a Cloud Automation workflow that pauses the rollback until an operator confirms the regressi
The Portage package manager stores package metadata in a SQLite database located at /var/db/portage/pkgdb . When Portage is upgraded, a forward migration script may alter the schema to add new fields or indexes. These migrations are currently one‑way; there is no built‑in reverse migration. A failed or incomplete migration can leave the database in an incons
Goal Define a reliable rollback strategy for Flyway migrations executed within a Dropwizard application using ManagedDataSource so that a failed schema change leaves no partial database state. Constraints and Uncertainty Dropwizard 2.x configures the data source with setAutoCommit(false) for explicit transaction control, yet DDL statements issued by Flyway o
sourceengine
git
pfsense
sqldeveloper
dynatrace
gentoo
dropwizard