How can I add a non-null column with a default using Doctrine Migrations without causing downtime?
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
doctrine