You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Greetings, I recently updated to 2.10 and found that my migrations no longer functioned properly. The background on that is most likely irrelevant, but essentially I'm using dynamic schema names and use the postGenerateSchema event to ensure my foreign keys are not reverted.
Q
A
BC Break
yes
Version
2.10.0
Summary
Doctrine\DBAL\Schema\ForeignKeyConstraint::getUnqualifiedForeignTableName is returning incorrect unqualified table names due to a change made to it in #3442(link to change) and causing \Doctrine\DBAL\Schema\Comparator::diffForeignKey to result in a false positive.
Current behaviour
Foreign table name - "schema.table_name"
Unqualified table name - ".table_name"
Expected behaviour
Foreign table name - "schema.table_name"
Unqualified table name - "table_name"
The text was updated successfully, but these errors were encountered:
Bug Report
Greetings, I recently updated to 2.10 and found that my migrations no longer functioned properly. The background on that is most likely irrelevant, but essentially I'm using dynamic schema names and use the postGenerateSchema event to ensure my foreign keys are not reverted.
Summary
Doctrine\DBAL\Schema\ForeignKeyConstraint::getUnqualifiedForeignTableName is returning incorrect unqualified table names due to a change made to it in #3442 (link to change) and causing \Doctrine\DBAL\Schema\Comparator::diffForeignKey to result in a false positive.
Current behaviour
Foreign table name - "schema.table_name"
Unqualified table name - ".table_name"
Expected behaviour
Foreign table name - "schema.table_name"
Unqualified table name - "table_name"
The text was updated successfully, but these errors were encountered: