Changes between Initial Version and Version 1 of Ticket #37286, comment 2


Ignore:
Timestamp:
Aug 19, 2026, 7:10:52 AM (3 weeks ago)
Author:
Yassin Bahri

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #37286, comment 2

    initial v1  
    11I reproduced this on current `main` using MySQL 8.4.
     2
     3This does not appear to be a regression, so I did not run `git bisect`.
     4The affected `db_index` removal logic predates support for
     5`UniqueConstraint` in `Meta.constraints`, introduced in Django 2.2 by
     6commit db13bca60a. The removal logic did not account for these constraints
     7when that feature was introduced.
     8
     9Therefore, the issue appears to have existed since this model configuration
     10first became supported rather than being caused by a later behavioral
     11regression.
    212
    313A schema-editor regression test creates both a field index and a same-column named `UniqueConstraint`, then removes `db_index`.
Back to Top