Changes between Version 3 and Version 4 of Ticket #36161


Ignore:
Timestamp:
Jan 30, 2025, 7:09:22 AM (12 hours ago)
Author:
Colin Watson
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #36161 – Description

    v3 v4  
    4848The workaround that we are currently using (see https://github.com/spanezz/django-reverse-migration-issue/blob/main/db/workaround.py and https://github.com/spanezz/django-reverse-migration-issue/blob/main/db/migrations/0002_alter_models.py#L34 ) involves introducing a migration operation that forces a reload of the affected model.
    4949
    50 This situation hints at some caching issue in the migration infrastructure which we've been unable to follow up, but which surfaces in real world scenarios and is extremely difficult to identify and handle when it does.
     50This situation hints at some caching issue in the migration infrastructure which we've been unable to follow up, but which surfaces in real world scenarios (see https://salsa.debian.org/freexian-team/debusine/-/merge_requests/1588#note_577725) and is extremely difficult to identify and handle when it does.
Back to Top