DDC-3966: After 2.5 upgrade: doctrine:schema:update --force fails because it detects invalid index name #4846

New Issue

admin · 2026-01-22T14:50:26+01:00

admin commented

2026-01-22 14:50:26 +01:00

Originally created by @doctrinebot on GitHub (Oct 30, 2015).

Originally assigned to: @beberlei on GitHub.

Jira issue originally created by user renoreckling:

We just upgraded to doctrine 2.5.1.
On our Postgresql DB, running doctrine:schema:update --force after we load our schema from migrations now fails with the following error:

  [Doctrine\DBAL\Exception\TableNotFoundException]                                                          
  An exception occurred while executing 'ALTER INDEX idx*55881faae3e6fba2 RENAME TO IDX*55881FAA2C5BC23E':  
  SQLSTATE[42P01]: Undefined table: 7 ERROR:  relation "idx_55881faae3e6fba2" does not exist

I think that should be impossible. I looked into the DB and there is no index named idx_55881faae3e6fba2 in the database.

The target name IDX_55881FAA2C5BC23E has previously existed but was removed some time ago via db migrations and the appropriate entity change.

This does not happen in doctrine/orm 2.4.4

Originally created by @doctrinebot on GitHub (Oct 30, 2015). Originally assigned to: @beberlei on GitHub. Jira issue originally created by user renoreckling: We just upgraded to doctrine 2.5.1. On our Postgresql DB, running doctrine:schema:update --force after we load our schema from migrations now fails with the following error: ``` [Doctrine\DBAL\Exception\TableNotFoundException] An exception occurred while executing 'ALTER INDEX idx*55881faae3e6fba2 RENAME TO IDX*55881FAA2C5BC23E': SQLSTATE[42P01]: Undefined table: 7 ERROR: relation "idx_55881faae3e6fba2" does not exist ``` I think that should be impossible. I looked into the DB and there is no index named idx_55881faae3e6fba2 in the database. The target name IDX_55881FAA2C5BC23E has previously existed but was removed some time ago via db migrations and the appropriate entity change. This does not happen in doctrine/orm 2.4.4

admin added the Bug label 2026-01-22 14:50:26 +01:00

admin commented

2026-01-22 14:50:27 +01:00

@doctrinebot commented on GitHub (Oct 30, 2015):

Comment created by renoreckling:

This seems to be caused by an existing foreign key that assumes the presence of an index on the id_column.

We have the situation:

Table A has a column b_id with foreign key constraint to table B.id.

Doctrine seems to assume that every foreign key is accompanied with a matching index, in this example on Table A.b_id, which is missing in our case.

@doctrinebot commented on GitHub (Oct 30, 2015): Comment created by renoreckling: This seems to be caused by an existing foreign key that assumes the presence of an index on the id_column. We have the situation: Table A has a column b_id with foreign key constraint to table B.id. Doctrine seems to assume that every foreign key is accompanied with a matching index, in this example on Table A.b_id, which is missing in our case.

admin referenced this issue

2026-01-22 14:55:26 +01:00

Mysql 5.7 requires order by clause in select DISTINCT statement (Paginator) #4981

admin referenced this issue

2026-01-22 14:59:41 +01:00

paginator incompatibility with MySQL 5.7 #5144

admin referenced this issue

2026-01-22 15:50:38 +01:00

Original exception is swallowed due rollback exception #7357

Sign in to join this conversation.