Changes between Initial Version and Version 6 of Ticket #26429


Ignore:
Timestamp:
Apr 18, 2016, 10:30:52 PM (9 years ago)
Author:
Daniel Izquierdo
Comment:

The docs in ​https://github.com/django/django/blob/2cd2d188516475ddf256e6267cd82c495fb5c430/django/db/migrations/autodetector.py#L1129 say that names are not guaranteed to be unique and the timestamp is just a best effort to avoid conflicts. So I think rtpg's suggested fix works well for merge migrations, and a test to ensure names don't conflict is not necessary.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #26429 – Description

    initial v6  
    1 After squashing migrations, further development can result in a merge migration with an identical name to a squashed migration.
    2 This is old merge is still stored in the django_migrations table and the new merge will not be applied.
    3 
    4 The workaround is to rename the merge to something unique. However the automatically generated names should not clash in the first place.
Back to Top