After Doctrine DBAL introspects a table, a database-created foreign-key index may look like an ordinary explicit index. Dropping only the foreign key and column can leave that index referencing a column that no longer exists.
Last updated: November 8, 2026.
<?php
$table = $schemaManager->introspectTableByUnquotedName('child');
foreach ($table->getIndexes() as $index) {
if (in_array('parent_id', $index->getColumnNames(), true)) {
$table->dropIndex($index->getName());
}
}
$table->removeForeignKey('child_parent');
$table->dropColumn('parent_id');Inspect the generated SQL before applying it. Index names and DBAL APIs vary by version and platform, so treat this as the ordering rule: remove dependent indexes and constraints first, then remove the column.
Why introspection changes the picture
The Doctrine schema-manager documentation shows how introspected tables expose columns, indexes, and foreign keys. A current DBAL issue explains that the database does not retain Doctrine’s “implicit index” label, so the index returns from introspection as explicit.
Removing the foreign key therefore may not remove its supporting index from the in-memory table. When the column is dropped next, schema validation or the database can reject the remaining index definition.
Generate and review a migration diff
Work from a fresh schema snapshot, list every index whose columns contain the target, and decide whether it exists only for the foreign key or also supports other queries. Drop only indexes that become invalid or are intentionally retired. Composite indexes need extra review because another column may still benefit from them.
Use DBAL’s comparator to generate SQL from the original and edited schemas. Review statement order, run it against a disposable copy, and verify foreign keys and indexes afterward. In production, use the project’s migration mechanism rather than dropping and recreating a populated table manually. Back up the schema definition before applying the migration.
Continue with detecting duplicate DBAL indexes, Doctrine transaction recovery, and composite-key design.
