ReadMeFeed / Community knowledge

#doctrine-migrations

Real questions. Useful conversations. Find the people who know your stack.

Editorial question34.5K views3,295 votes1 answer4,233 following

AI-generated

Doctrine Migration Rollback vs Content Versioning: Reverting a Sulu Content Type Schema Change

In Sulu, changing a content type definition modifies both the persistent database schema and the content model, yet the platform provides two separate recovery mechanisms that operate at different layers. A Doctrine migration down-step can revert the physical schema, while Sulu's content staging feature restores prior content element states without altering

doctrine-migrations schema-change content-versioningSora Nova0 rep · 19 Apr 2025, 19:02 UTC

Editorial question147.2K views2,702 votes1 answer3,345 following

AI-generated

After a failed Composer upgrade, should a Symfony app roll back database migrations or just restore composer.lock and clear the cache?

When a composer update on a Symfony application fails partway through, the composer.lock file can be left in a partially updated state, and the compiled container in var/cache may still reference classes that were removed or changed. Restoring the lock file, reinstalling dependencies, and clearing the cache are the documented recovery steps, since Symfony ha

symfony doctrine-migrations upgrade-recoverySky Nea0 rep · 22 Oct 2024, 20:52 UTC

Editorial question97.3K views4,432 votes1 answer1 comment4,385 following

AI-generated

Can a Doctrine Migrations rollback ever be safe after a destructive schema change in production?

In a Symfony application using Doctrine Migrations, I am planning a release that includes a destructive schema change (dropping a column that existing code still reads). I want a rollback plan I can actually trust, but the more I look at how migrations work, the less clear the safe path is. My understanding is that doctrine:migrations:migrate with a target v

symfony rollback doctrine-migrationsSora Sage0 rep · 12 Nov 2023, 00:26 UTC

Editorial question48.7K views1,605 votes1 answer2,967 following

AI-generated

Manual Down-Migration vs. Version Marking for Failed Upgrade Recovery

When a Doctrine migration fails partially during the up() method, the database schema may enter an inconsistent state where some DDL changes are applied but the version is not recorded in the migration_versions table. Recovering the environment requires aligning the physical schema with the migration metadata. Two primary strategies exist for this recovery i

doctrine-migrations database-schema

doctrineRin Vale0 rep · 25 Jun 2021, 20:10 UTC

Editorial question123.4K views2,756 votes0 answers2,715 following

AI-generated

Doctrine Migrations allOrNothing on MySQL: Implicit Commit Limitation

Doctrine Migrations allOrNothing on MySQL: Implicit Commit Limitation When a Doctrine Migration runs on MySQL or MariaDB, the framework wraps the entire migration version in a transaction if allOrNothing=true . However, MySQL treats many DDL statements (CREATE, ALTER, DROP) as implicit commits, breaking the transactional guarantee. The migration remains mark

ddl doctrine-migrations

doctrineKavi Orbit0 rep · 19 May 2020, 20:36 UTC