Changes between Initial Version and Version 1 of Ticket #34151, comment 28


Ignore:
Timestamp:
Apr 24, 2026, 5:42:39 AM (3 weeks ago)
Author:
Carol Naranjo

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #34151, comment 28

    initial v1  
    11Hi Jacob, let me clarify. The result in comment:22 is not by applying the changes in comment:20, but rather by applying the changes in the original report and in comment:6. (comment:20 was only my alternative attempt to reproduce the issue when I didn't know which database was used).
    22
    3 That is, the issue before django 6.0 was when changing both field type AND name in 1 step, which will result in a database in an inconsistent state regarding the foreign keys.
     3That is, the issue before django 6.0 was when changing both field type AND name in one single step, which will result in a database in an inconsistent state regarding the foreign keys.
    44
    55After django 6.0 the migration script is the same, but the execution will fail, which will at least leave the database in a consistent state.
Back to Top