A migration causes implicit changes to existing database tables that are not related to the migration
Current behavior
During the execution of a migration, SchemaDiffProvider is providing a diff of all tables in the database that results in my case in an ALTER TABLE statement to be executed, affecting a table that is not related to the migration that I am executing (neither to my application).
Background:
I share a single database with different other teams. I have a set of tables I manage with doctrine, however, other teams might do the same with their tables. I have no control over which tables other teams have created or will create in the future.
How to reproduce
Manually create table table1 in your database that has a column with type longtext and COMMENT '(DC2Type:json)'
Create a migration that creates table table2.
Run the migration (with --write-sql)
4.. Notice the ALTER TABLE statement for table1
Expected behavior
Running a migration only affects changes that the migration describes
Bug Report
Summary
A migration causes implicit changes to existing database tables that are not related to the migration
Current behavior
During the execution of a migration, SchemaDiffProvider is providing a diff of all tables in the database that results in my case in an ALTER TABLE statement to be executed, affecting a table that is not related to the migration that I am executing (neither to my application).
Background: I share a single database with different other teams. I have a set of tables I manage with doctrine, however, other teams might do the same with their tables. I have no control over which tables other teams have created or will create in the future.
How to reproduce
table1
in your database that has a column with typelongtext
and COMMENT '(DC2Type:json)'table2
.--write-sql
) 4.. Notice theALTER TABLE
statement fortable1
Expected behavior
Running a migration only affects changes that the migration describes