ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Doctrine Migrations lets you version‑control database changes in Symfony, apply them safely, and roll back if needed. This guide covers the desired outcome, prerequisites, step‑by‑step procedure, checks, and recovery options.
Learn how to use CodeIgniter 4 migrations to maintain database schema consistency across environments using the Forge schema builder and CLI tools.
I need to modify the schema of a small application that must stay online, and I want to use Doctrine Migrations to perform the change. The table contains a moderate amount of data, and I cannot afford a long lock that would block reads or writes. I am unsure which sequence of migration steps—adding the column as nullable, deploying updated code, backfilling
Rollback scope after a schema change I am defining a rollback policy for a Rails application (assume a current Rails 7.x line with PostgreSQL) and need to pin down exactly what rails db:rollback is allowed to promise. Our migrations are written with change where possible, but some use remove_column , change_column , and occasionally execute for data cleanup.
The goal is to achieve zero‑downtime deployments while preserving the ability to roll back a schema change safely in a NestJS application that uses TypeORM. Two documented approaches exist: enabling the synchronize flag so TypeORM updates the schema automatically on startup, or generating explicit up/down migration scripts and running them via the NestJS/Typ
symfony
doctrine
codeigniter
rails
nestjs