-
-
Notifications
You must be signed in to change notification settings - Fork 395
Closed
Description
BC Break Report
| Q | A |
|---|---|
| BC Break | yes |
| Version | 3.0.0 |
Summary
When I updated doctrine/orm to version 3.0.0, my CI started to fail due to the doctrine:schema check:validate, which returned DROP TABLE doctrine_migration_versions;
I found that adding schema_filter can fix this problem: "^(?!doctrine_migration_versions$)" in the dbal configuration, indeed, then the error no longer appears, but after that my migrations stopped tracking the current state and think that at the moment no migration has been performed.
In version 3.0, the saveMode argument was removed in \Doctrine\ORM\Tools\SchemaTool::getUpdateSchemaSql and because of this, doctrine:schema:validate tracks deleted tables and returns sql for this action.

Previous behavior
Current behavior
How to reproduce
- composer require doctrine/doctrine-migrations-bundle
- composer require doctrine/orm-pack
- bin/console doctrine:migration:diff
- bin/console doctrine:migration:migrate
- bin/console doctrine:schema:validate -v
vadim-gapanovich, Erzikov, mrVrAlex, deasraze, chopperqt and 56 morepsprokofiev, yapro, ecourtial and LeikoDmitryyapro, ecourtial, armandojg12, Rainrider, gndk and 3 more
Metadata
Metadata
Assignees
Labels
No labels